Displaying 5 results from an estimated 5 matches for "setlittleendian".
2015 Jul 29
0
[LLVMdev] The Trouble with Triples
...r.
>
> llvm::TargetTuple TT(GnuTriple);
> // Then mutate the TargetTuple according to the compiler options (or
> equivalent depending
>
> // on the tool, for example disassemblers would mutate it according to the
> object headers).
> if (hasOption("-EL"))
> TT.setLittleEndian()
>
> ...
>
> At this point, TT would be
> "+mipsel-unknown-linux-gnu-elf32-some-other-stuff" (exact serialization is
> t.b.d and may end up target dependent) which we can then rely on in the
> rest of LLVM. This split resolves the issue of llvm::Triple objects not
&g...
2015 Jul 08
5
[LLVMdev] The Trouble with Triples
...y customized) meanings in
// use by the vendor.
llvm::TargetTuple TT(GnuTriple);
// Then mutate the TargetTuple according to the compiler options (or equivalent depending
// on the tool, for example disassemblers would mutate it according to the object headers).
if (hasOption("-EL"))
TT.setLittleEndian()
...
At this point, TT would be "+mipsel-unknown-linux-gnu-elf32-some-other-stuff" (exact serialization is t.b.d and may end up target dependent) which we can then rely on in the rest of LLVM. This split resolves the issue of llvm::Triple objects not being reliable when used as a target...
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
...y customized) meanings in
// use by the vendor.
llvm::TargetTuple TT(GnuTriple);
// Then mutate the TargetTuple according to the compiler options (or equivalent depending
// on the tool, for example disassemblers would mutate it according to the object headers).
if (hasOption("-EL"))
TT.setLittleEndian()
...
At this point, TT would be "+mipsel-unknown-linux-gnu-elf32-some-other-stuff" (exact serialization is t.b.d and may end up target dependent) which we can then rely on in the rest of LLVM. This split resolves the issue of llvm::Triple objects not being reliable when used as a target...
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
...the vendor.
> llvm::TargetTuple TT(GnuTriple);
> // Then mutate the TargetTuple according to the compiler options (or
> equivalent depending
> // on the tool, for example disassemblers would mutate it according to the
> object headers).
> if (hasOption("-EL"))
> TT.setLittleEndian()
> ...
> At this point, TT would be
> "+mipsel-unknown-linux-gnu-elf32-some-other-stuff" (exact serialization is
> t.b.d and may end up target dependent) which we can then rely on in the
> rest of LLVM. This split resolves the issue of llvm::Triple objects not
> being r...
2015 Jul 31
2
[LLVMdev] The Trouble with Triples
...y customized) meanings in
// use by the vendor.
llvm::TargetTuple TT(GnuTriple);
// Then mutate the TargetTuple according to the compiler options (or equivalent depending
// on the tool, for example disassemblers would mutate it according to the object headers).
if (hasOption("-EL"))
TT.setLittleEndian()
...
At this point, TT would be "+mipsel-unknown-linux-gnu-elf32-some-other-stuff" (exact serialization is t.b.d and may end up target dependent) which we can then rely on in the rest of LLVM. This split resolves the issue of llvm::Triple objects not being reliable when used as a target...