[LLVMdev] MIPS & GP register

[Carl Norum]

On Aug 16, 2012, at 10:58 AM, Eli Friedman wrote:
> That's weird... you're probably triggering some sort of bad case in
> the driver logic which tries to call gcc to assemble and link on
> targets where we don't know what to do.  That logic is generally a bit
> shaky to begin with.

It sounds like that means "time to file a bug". =)  Which product should I file under?

>>> For the MIPS-specific flags, I don't think there's an equivalent;
>>> please file bugs if it's actually useful functionality we should
>>> be exposing with regular flags.
>> 
>> Both of those flags are critical, I think.  It's possible the delay slot filler isn't believed to be "ready for prime time" and so it's hidden?  It does seem to work fine for us.  Setting the SDATA section threshold is very important for us - our program is much too large and has far too many globals to fit in the 64 KB SDATA section.  I'll file bugs and see what turns up.  I can make the patches myself if you can give me the 30-second pointer in the right direction.
> 
> Clang::AddMIPSTargetArgs does the relevant parsing; options are
> defined in include/clang/Driver/Options.td .

Thanks - I'll give it a look and shed what I can do before filing bugs about them.

-- Carl