[llvm] r181753 - This is the first of three patches which creates stubs used for

[Rafael Espíndola]

> I probably air too much of what I'm doing on the list as far as design and
> my attempt is never to hide such things. I really could not have imagined
> such a big discussion about generating some tiny stubs . It only came up
> during the issue of the APP/NO_APP wrappers.

I still think you are doing this wrong and it will be harder to
implement it correctly once you have this in. IMHO the only thing
needing special treatment for the stubs in the backend would be
calling convention. Other than that they would be regular mips16 or
mips32 *IL* functions. Mixing mips16 and mip32 should not be that
different from mixing thumb and arm.

But you are correct, I don't have big objections to you guys
implementing this in the way you think is best, *as long as it stays
local to mips*. In particular, two things that came up in this
discussion that really don't want to see in trunk are:

* the ability for the compiler to tell if an inline asm is compiler
generated or human written. (the APP/NO_APP discussion). I am ok with
avoiding printing them, as long as we avoid for all inline asm (by not
printing it at all for mips target for example).

* the extension of the section attribute to be an arbitrary string
passed to the assembler or the addition of section related attributes
(i.e., llvm.org/pr15788 should be closed as wontfix).

Cheers,
Rafael