On Fri, 25 Jan 2013, Richard Sandiford wrote:
> > FWIW, I think the benefit from these attributes being a type property is
> > questionable to say the least. My understanding is the only application
> > is to prevent the tail-call optimisation from being applied to non-PIC
> > standard MIPS f
; > What is not clear then?
>> >
>> > This is how all such other attributes in gcc are handled.
>>
>> Well, in a way, these are the only such attributes in GCC :-)
>> I don't think any other port supports switching between different
>> ISA modes l
l such other attributes in gcc are handled.
>
> Well, in a way, these are the only such attributes in GCC :-)
> I don't think any other port supports switching between different
> ISA modes like this.
>
> I think the original authors really wanted "mips16" and "n
On Tue, 15 Jan 2013, David Daney wrote:
> > I'm not understanding why mips16 and nomips16 are not simple inheritable
> > attributes.
>
> The mips16ness of a function must be known by the caller so that the
> appropriate version of the JAL/JALX instruction can be emitt
Sorry for the slow reply, only just saw this.
reed kotler writes:
> On 01/14/2013 04:50 PM, David Daney wrote:
>> On 01/14/2013 04:32 PM, reed kotler wrote:
>>> I'm not understanding why mips16 and nomips16 are not simple inheritable
>>> attributes.
>>
&
On 01/14/2013 04:50 PM, David Daney wrote:
On 01/14/2013 04:32 PM, reed kotler wrote:
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
The mips16ness of a function must be known by the caller so that the
appropriate version of the JAL/JALX instructio
On 01/14/2013 04:32 PM, reed kotler wrote:
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
The mips16ness of a function must be known by the caller so that the
appropriate version of the JAL/JALX instruction can be emitted
i..e you should be ab
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
i..e you should be able to say:
void foo();
void __attribute((nomips16)) foo();
or
void goo();
void __attribute((mips16)) goo();
There does not seem to be any other cases in gcc where this would n
