Lines Matching +refs:clang +refs:rename +refs:format +refs:message

20 The second piece is the `Clang <http://clang.llvm.org/>`_ front end.  This
33 Getting Started <http://clang.llvm.org/get_started.html>`_ page might also be a
53    * ``svn co http://llvm.org/svn/llvm-project/cfe/trunk clang``
238 * **mv** --- move (rename) files
383 If you fail to set rpath, most LLVM binaries will fail on startup with a message
519 If you want to check out clang too, run:
524   % git clone http://llvm.org/git/clang.git
587 But you may generate patchset with git-format-patch. It generates by-each-commit
592   % git format-patch --no-attach master..mybranch -o /path/to/your/patchset
599   % git format-patch --attach master..mybranch --stdout | git imap-send
633   # If you have clang too:
635   % git clone http://llvm.org/git/clang.git
636   % cd clang
648   % git fetch && (cd tools/clang && git fetch)  # Get matching revisions of both trees.
651   % (cd tools/clang &&
669 escape into the commit message, one can use the script ``git-svnrevert`` or
671 revert, look up the appropriate svn revision, and output a message where all
705 generates the build files in whatever format you request as well as various
708 Variables are passed to ``cmake`` on the command line using the format
869 <http://clang.llvm.org/docs/CrossCompilation.html>`_ for more information
1164 Example with clang
1182      % clang hello.c -o hello
1193      % clang -O3 -emit-llvm hello.c -c -o hello.bc
1240    Note that using clang to compile directly to native code (i.e. when the