Displaying 5 results from an estimated 5 matches for "7472756e".
2016 Oct 28
0
Compiler used to build LLVM
...2d332900 636c616e at 6.1.1-3).clan
0030 67207665 7273696f 6e20342e 302e3020 g version 4.0.0
0040 28747275 6e6b2032 38353332 36292028 (trunk 285326) (
0050 6c6c766d 2f747275 6e6b2032 38353331 llvm/trunk 28531
0060 38290063 6c616e67 20766572 73696f6e 8).clang version
0070 20342e30 2e302028 7472756e 6b203238 4.0.0 (trunk 28
0080 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...
2016 Oct 28
1
Compiler used to build LLVM
...at 6.1.1-3).clan
> 0030 67207665 7273696f 6e20342e 302e3020 g version 4.0.0
> 0040 28747275 6e6b2032 38353332 36292028 (trunk 285326) (
> 0050 6c6c766d 2f747275 6e6b2032 38353331 llvm/trunk 28531
> 0060 38290063 6c616e67 20766572 73696f6e 8).clang version
> 0070 20342e30 2e302028 7472756e 6b203238 4.0.0 (trunk 28
> 0080 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 766d2f7...
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 29
1
Embedding LLD version to executables
On Wed, Oct 26, 2016 at 4:16 AM, Joerg Sonnenberger via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Tue, Oct 25, 2016 at 06:07:09PM -0400, Rafael Espíndola via llvm-dev
> wrote:
> > I am ok with both ".note.linker-version" and adding an entry to .comment.
>
> There is one important different between the two -- strip normally has
> to preserve the
2016 Oct 26
2
Embedding LLD version to executables
On Tue, Oct 25, 2016 at 06:07:09PM -0400, Rafael Espíndola via llvm-dev wrote:
> I am ok with both ".note.linker-version" and adding an entry to .comment.
There is one important different between the two -- strip normally has
to preserve the former, but not the latter. As such, I'd quite a bit
prefer using .comment.
Joerg