Displaying 3 results from an estimated 3 matches for "fredsos".
Did you mean:
fred's
2015 Jul 31
2
[LLVMdev] The Trouble with Triples
...rOS version 1 would change too and would have to either stop updates or maintain patches to keep it's default target. Alternatively, BarOS version 2 must maintain patches. We need a mechanism for BarOS to decide which Foo revision they want.
Now suppose, there's another distribution called FredsOS. It too has the triple foo-linux-gnu but wants to target Foo revision 3. If clang changed to accommodate BarOS, then FredsOS is in the same position as BarOS version 2 was.
The same thing happens with cross-compilers. Using the mips-mti-linux-gnu toolchain as an example:
Mentor release a mips-mti-...
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
Hi Daniel,
> (from the context, you might have meant 'tuple' where you've written
> 'triple'. I'm answering based on the assumption you meant 'triple')
>
>
I did mean what I wrote.
> The GNU triple is already used as a way of encoding a large amount of the
> target data in a string but unfortunately, while this data is passed
> throughout
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
Hi Eric,
Thanks for getting back to me on this.
> I'm not sure I agree with the basic idea of using the target triple as a way of
> encoding all of the pieces of target data as a string. I think in a number of
> cases what we need to do is either open up API to the back end to specify things,
> or encode the information into the IR when it's different from the generic triple.