Displaying 6 results from an estimated 6 matches for "gnutriple".
Did you mean:
gettriple
2015 May 23
3
[LLVMdev] Moving Private Label Prefixes from MCAsmInfo to MCObjectFileInfo
On 23 May 2015 at 00:08, Jim Grosbach <grosbach at apple.com> wrote:
> This is the key question. The LLVM assumption is that these sorts of things
> are inferable from the triple. Your observation here that the GNU world’s
> notion of triples and LLVM’s need not be the same is a good one. Having a
> split and a translation up in clang seems an interesting avenue to explore.
>
2015 Jul 29
0
[LLVMdev] The Trouble with Triples
...the vendor's rules,
> providing an interface to allow mutation by tools, and authoritatively
> defining the target being targeted without the ambiguity of GNU Triples. As
> an example, 'mips-linux-gnu-clang –EL …' would:
>
> // Parse the GNU Triple
>
> llvm::Triple GnuTriple("mips-linux-gnu");
>
> // Convert it to a TargetTuple according to the (possibly customized)
> meanings in
>
> // use by the vendor.
>
> llvm::TargetTuple TT(GnuTriple);
> // Then mutate the TargetTuple according to the compiler options (or
> equivalent dependin...
2015 Jul 08
5
[LLVMdev] The Trouble with Triples
...erpreting the triple according to the vendor's rules, providing an interface to allow mutation by tools, and authoritatively defining the target being targeted without the ambiguity of GNU Triples. As an example, 'mips-linux-gnu-clang -EL ...' would:
// Parse the GNU Triple
llvm::Triple GnuTriple("mips-linux-gnu");
// Convert it to a TargetTuple according to the (possibly 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 w...
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
...nterpreting the triple according to the vendor's rules, providing an interface to allow mutation by tools, and authoritatively defining the target being targeted without the ambiguity of GNU Triples. As an example, 'mips-linux-gnu-clang –EL …' would:
// Parse the GNU Triple
llvm::Triple GnuTriple("mips-linux-gnu");
// Convert it to a TargetTuple according to the (possibly 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 w...
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
...cording to the vendor's rules,
> providing an interface to allow mutation by tools, and authoritatively
> defining the target being targeted without the ambiguity of GNU Triples. As
> an example, 'mips-linux-gnu-clang –EL …' would:
> // Parse the GNU Triple
> llvm::Triple GnuTriple("mips-linux-gnu");
> // Convert it to a TargetTuple according to the (possibly customized)
> meanings in
> // use by the vendor.
> llvm::TargetTuple TT(GnuTriple);
> // Then mutate the TargetTuple according to the compiler options (or
> equivalent depending
> // on th...
2015 Jul 31
2
[LLVMdev] The Trouble with Triples
...erpreting the triple according to the vendor's rules, providing an interface to allow mutation by tools, and authoritatively defining the target being targeted without the ambiguity of GNU Triples. As an example, 'mips-linux-gnu-clang -EL ...' would:
// Parse the GNU Triple
llvm::Triple GnuTriple("mips-linux-gnu");
// Convert it to a TargetTuple according to the (possibly 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 w...