search for: 00636c61

Displaying 4 results from an estimated 4 matches for "00636c61".

2016 Oct 28
0
Compiler used to build LLVM
...34323239 2920286c 6c766d2f 7472756e 4229) (llvm/trun 0090 6b203238 34323438 2900636c 616e6720 k 284248).clang 00a0 76657273 696f6e20 342e302e 30202874 version 4.0.0 (t 00b0 72756e6b 20323832 30383929 20286c6c runk 282089) (ll 00c0 766d2f74 72756e6b 20323832 30393829 vm/trunk 282098) 00d0 00636c61 6e672076 65727369 6f6e2034 .clang version 4 00e0 2e302e30 20287472 756e6b20 32383335 .0.0 (trunk 2835 00f0 37342920 286c6c76 6d2f7472 756e6b20 74) (llvm/trunk 0100 32383335 39392900 283599). It should be easy to enable for your platform if it's disabled/not there. --...
2016 Oct 28
1
Compiler used to build LLVM
...c766d2f 7472756e 4229) (llvm/trun > 0090 6b203238 34323438 2900636c 616e6720 k 284248).clang > 00a0 76657273 696f6e20 342e302e 30202874 version 4.0.0 (t > 00b0 72756e6b 20323832 30383929 20286c6c runk 282089) (ll > 00c0 766d2f74 72756e6b 20323832 30393829 vm/trunk 282098) > 00d0 00636c61 6e672076 65727369 6f6e2034 .clang version 4 > 00e0 2e302e30 20287472 756e6b20 32383335 .0.0 (trunk 2835 > 00f0 37342920 286c6c76 6d2f7472 756e6b20 74) (llvm/trunk > 0100 32383335 39392900 283599). > > It should be easy to enable for your platform if it's di...
2016 Oct 28
4
Compiler used to build LLVM
Hello, We’d like to keep track of which clang version was used to build our LLVM binaries. We use cmake and ninja with clang to build. What do you people think would be the cleanest way to know which version of clang is used, on a user’s machine, to build those binaries. I’m hoping to script this. I was thinking that getting cmake/ninja to spit out this information, if possible, would probably be
2016 Oct 19
2
Embedding LLD version to executables
----- Original Message ----- > From: "Mehdi Amini" <mehdi.amini at apple.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Rui Ueyama" > <ruiu at google.com> > Sent: Tuesday, October 18, 2016 10:38:57 PM > Subject: Re: [llvm-dev] Embedding LLD version to executables >