Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-03-25T15:23:34+00:00 2019-03-25T15:23:34+00:00 Serge Guelton sguelton@redhat.com 2019-03-25T15:23:34+00:00 urn:sha1:3a22c3cc2b06bd871cabddac3a541cdf03399b77 Differential Revision: https://reviews.llvm.org/D59582 llvm-svn: 356910 2019-03-21T18:27:40+00:00 Serge Guelton sguelton@redhat.com 2019-03-21T18:27:40+00:00 urn:sha1:525cd59f5a12254e80d5f20bf2d9713728a114d4 Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 2016-09-06T20:57:50+00:00 Kate Stone katherine.stone@apple.com 2016-09-06T20:57:50+00:00 urn:sha1:b9c1b51e45b845debb76d8658edabca70ca56079 *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751 2011-10-28T23:30:28+00:00 Johnny Chen johnny.chen@apple.com 2011-10-28T23:30:28+00:00 urn:sha1:8763780961ae37b46690e0ee66447847275a0040 commands to print the binary representaion of an integer. llvm-svn: 143252 2011-10-28T01:09:53+00:00 Johnny Chen johnny.chen@apple.com 2011-10-28T01:09:53+00:00 urn:sha1:2a781097f37bab041ed2cafb7cbcd95096fad46c llvm-svn: 143173