Re: mips16 and nomips16

2013-02-20 Thread Maciej W. Rozycki
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

Re: mips16 and nomips16

2013-01-25 Thread Richard Sandiford
"Maciej W. Rozycki" writes: > On Fri, 18 Jan 2013, Richard Sandiford wrote: > >> > I would assume that foo would be nomips16 and goo would be mips16. >> > >> > The definition of plain foo() or goo() says that nothing is specified. >> > >> > What is not clear then? >> > >> > This is how all such ot

Re: mips16 and nomips16

2013-01-25 Thread Maciej W. Rozycki
On Fri, 18 Jan 2013, Richard Sandiford wrote: > > I would assume that foo would be nomips16 and goo would be mips16. > > > > The definition of plain foo() or goo() says that nothing is specified. > > > > What is not clear then? > > > > This is how all such other attributes in gcc are handled. > >

Re: mips16 and nomips16

2013-01-25 Thread Maciej W. Rozycki
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 emitted Not really, the issue of

Re: mips16 and nomips16

2013-01-18 Thread Richard Sandiford
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. >> >> The mips16ness of a function must be know

Re: mips16 and nomips16

2013-01-14 Thread reed kotler
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 instruction can b

Re: mips16 and nomips16

2013-01-14 Thread David Daney
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 able to sa