[llvm-commits] [llvm] r123990 - in /llvm/trunk: include/llvm/ADT/Triple.h lib/Support/Triple.cpp unittests/ADT/TripleTest.cpp

[Renato Golin]

On 24/01/11 21:16, Sandeep Patel wrote:
>  > Android started using arm-linux-androideabi recently, old one was
> arm-eabi.
>
> We were prototyping with "arm-eabi" which actually expands to
> "arm-unknown-eabi" not "arm-none-eabi".

Hum, ok, I'm confused. Does this mean that "eabi" is bare-metal eabi,
"linuxeabi" is Linux eabi and "gnueabi" is what?

If that's the case, than "eabi" is in fact telling the OS by saying
there is NO OS, but that's misleading...

Anyway, I'm not trying to re-write target triple, just understanding it
enough to parse it correctly in LLVM.

It'd be good to have the same parser for both Clang and LLC when I pass
a non-normalized triple to them (if it's a configuration option in a
makefile).

In my (very humble) view, we either parse the triple and understand it,
or we bail out with an error message. I don't like at all the tons of
silent decisions Clang makes, as much as I don't like the tons of
guessing GCC does with ARM assembly.

But that's another discussion entirely...

cheers,
--renato

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.