Home
last modified time | relevance | path

Searched refs:rebase (Results 1 – 25 of 35) sorted by relevance

12

/external/swiftshader/third_party/llvm-7.0/llvm/test/tools/llvm-objdump/
Dmacho-bad-bind.test70 RUN: not llvm-objdump -macho -rebase %p/Inputs/macho-rebase-set-type-imm 2>&1 | FileCheck -check-pr…
71 REBASE-SET-TYPE-IMM: macho-rebase-set-type-imm': truncated or malformed object (for REBASE_OPCODE_S…
73 RUN: not llvm-objdump -macho -rebase %p/Inputs/macho-rebase-uleb-malformed-uleb128 2>&1 | FileCheck…
74 REBASE-ULEB-MALFORMED-ULEB128: macho-rebase-uleb-malformed-uleb128': truncated or malformed object …
76 RUN: not llvm-objdump -macho -rebase %p/Inputs/macho-rebase-seg-too-big 2>&1 | FileCheck -check-pre…
77 REBASE-SEG-TOO-BIG: macho-rebase-seg-too-big': truncated or malformed object (for REBASE_OPCODE_SET…
79 RUN: not llvm-objdump -macho -rebase %p/Inputs/macho-rebase-segoff-too-big 2>&1 | FileCheck -check-…
80 REBASE-SEGOFF-TOO-BIG: macho-rebase-segoff-too-big': truncated or malformed object (for REBASE_OPCO…
82 RUN: not llvm-objdump -macho -rebase %p/Inputs/macho-rebase-add-addr-uleb 2>&1 | FileCheck -check-p…
83 REBASE-ADD-ADDR-ULEB: macho-rebase-add-addr-uleb': truncated or malformed object (for REBASE_OPCODE…
[all …]
Dmacho-rebase.test1 # RUN: llvm-objdump -macho -rebase -arch x86_64 \
2 # RUN: %p/Inputs/rebase.macho-x86_64 | FileCheck %s
/external/llvm/test/tools/llvm-objdump/
Dmacho-rebase.test1 # RUN: llvm-objdump -macho -rebase -arch x86_64 \
2 # RUN: %p/Inputs/rebase.macho-x86_64 | FileCheck %s
/external/clang/
DRenderScriptPrebuilts.md50 prebuilts generated for this rebase, or to the latest platform version if no
81 (i.e. without the rebase), push them to a device with the rebased tools, and
88 This ensures that the rebase did not break the 2.9 and 3.2 BitcodeWriters.
94 The following projects will almost always have CLs as a part of the rebase.
DToolchainPrebuilts.md177 This was broken by a rebase once, and worth testing after every rebase.
189 The following projects will almost always have CLs as a part of the rebase.
/external/tcpdump/
DCONTRIBUTING91 8) Try to rebase your commits to keep the history simple.
92 git rebase upstream/master
93 (If the rebase fails and you cannot resolve, issue "git rebase --abort"
/external/llvm/utils/git-svn/
Dgit-svnup12 git svn rebase -l
/external/swiftshader/third_party/llvm-7.0/llvm/utils/git-svn/
Dgit-svnup12 git svn rebase -l
/external/ltp/doc/
Dc-test-tutorial-simple.txt305 Git-rebase, which allows us to clean up the commit history. So don't worry
822 After that we have the pleasure of doing an interactive 'rebase' to clean up
831 tutorial and 'rebase' it. You should try following along with your own
838 152d39fe7 (HEAD -> tutorial-rebase2, tutorial-rebase) tutorial: Start Submitting patch section
844 1e24a5fb5 (me/tutorial-rebase) fixup! tutorial
858 'rebase' and submitted a patch for review, so my original branch was just called
873 $ git rebase -i 5ca627b78\^
877 This begins an interactive 'rebase' where commit 5ca6427b78 is the earliest
879 commit before this one. The interactive 'rebase' command takes the last commit
888 [source,rebase]
[all …]
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/X86/
Dconstant-hoisting-optnone.ll5 ; constant 0xBEEBEEBEC, and then rebase the other constant
/external/llvm/test/CodeGen/X86/
Dconstant-hoisting-optnone.ll5 ; constant 0xBEEBEEBEC, and then rebase the other constant
/external/mesa3d/src/mesa/drivers/dri/i965/
Dbrw_misc_state.c157 bool rebase = tile_x & 7 || tile_y & 7; in rebase_depth_stencil() local
160 rebase |= (!devinfo->has_surface_tile_offset && (tile_x || tile_y)); in rebase_depth_stencil()
162 if (rebase) { in rebase_depth_stencil()
/external/autotest/client/common_lib/
Drevision_control.py194 def pull(self, rebase=False): argument
204 if rebase:
/external/deqp-deps/SPIRV-Tools/
DCONTRIBUTING.md179 back to the author and ask them to rebase. During the interactive rebase be
183 git rebase -i master
/external/swiftshader/third_party/SPIRV-Tools/
DCONTRIBUTING.md179 back to the author and ask them to rebase. During the interactive rebase be
183 git rebase -i master
/external/syzkaller/docs/
Dcontributing.md66 - If you decided to rebase commits in `my-branch` (e.g. to rebase them onto updated master) after y…
/external/swiftshader/third_party/llvm-7.0/llvm/docs/
DGettingStarted.rst547 pull --rebase`` instead of ``git pull`` to avoid generating a non-linear history
548 in your clone. To configure ``git pull`` to pass ``--rebase`` by default on the
553 % git config branch.master.rebase true
622 % git svn rebase -l # -l avoids fetching ahead of the git mirror.
630 % git svn rebase -l
641 % git svn rebase -l
644 git svn rebase -l)
649 ``checkout`` each working branch individually and ``rebase`` it on top of its
675 On success, ``dcommit`` will rebase against the HEAD of SVN, so to avoid conflict,
676 please make sure your current branch is up-to-date (via fetch/rebase) before
[all …]
/external/llvm/docs/
DGettingStarted.rst556 pull --rebase`` instead of ``git pull`` to avoid generating a non-linear history
557 in your clone. To configure ``git pull`` to pass ``--rebase`` by default on the
562 % git config branch.master.rebase true
631 % git svn rebase -l # -l avoids fetching ahead of the git mirror.
639 % git svn rebase -l
650 % git svn rebase -l
653 git svn rebase -l)
658 ``checkout`` each working branch individually and ``rebase`` it on top of its
684 On success, ``dcommit`` will rebase against the HEAD of SVN, so to avoid conflict,
685 please make sure your current branch is up-to-date (via fetch/rebase) before
[all …]
/external/flatbuffers/
DCONTRIBUTING.md36 (`git rebase -i`) such that your PR is a single commit on top of the current
/external/flatbuffers/docs/source/
DCONTRIBUTING.md36 (`git rebase -i`) such that your PR is a single commit on top of the current
/external/swiftshader/third_party/llvm-7.0/llvm/docs/Proposals/
DGitHubMove.rst516 git svn rebase -l # -l avoids fetching ahead of the git mirror.
574 git svn rebase -l
589 Before you push, you'll need to fetch and rebase (`git pull --rebase`) as
606 "rebase" implicitly happens while committing (unless a conflict occurs).
630 git svn rebase -l
637 git svn rebase -l
644 git svn rebase -l
/external/boringssl/src/
DCONTRIBUTING.md41 version of it. (Use the `git rebase` or `git commit --amend` commands.)
/external/syzkaller/vendor/google.golang.org/grpc/
DCONTRIBUTING.md25 …h messy commit history are difficult to review and won't be merged. Use `rebase -i upstream/master…
/external/u-boot/tools/patman/
DREADME342 git rebase -i HEAD~6
346 git rebase --continue
397 git rebase origin/master
399 and use git rebase -i to edit the commits, dropping the wip one. You add
/external/libaom/libaom/
DREADME.md593 In general, you should not rebase your changes when doing updates in response to
600 Gerrit UI. This will usually automatically rebase your change onto the branch
604 must rebase your changes manually:
608 $ git rebase origin/branchname

12