[llvm-commits] [llvm] r120230 - in /llvm/trunk/tools/llvmc/src: Base.td.in Hooks.cpp

[Eric Christopher]

On Nov 30, 2010, at 9:29 AM, Anton Korobeynikov wrote:

> Hi Eric,
> 
>> This is probably an involved task - it'll probably involve doing things like separating out instruction itineraries from the processor description for ARM, making sure that things that call into the backend use the tuning information if it's requested as opposed to the architecture information, etc.
> Isn't this just a matter of attributes aliases? E.g. armv6 would be
> translated into arm + v6 attr and so on? I dunno whether this is the
> similar in MIPS world, you definitely know better :)

Sure, but that's no different than specifying a processor at the moment - the processor details in the backend do exactly that. I assumed this was a step in some direction towards supporting all of the options which would make it a choice of how we want to go about doing it. I don't think you should be translating that in the front end, you just need options supported by each backend.

-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20101130/bc923fdd/attachment.html>