This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [mep] don't inline VLIW code into non-VLIW routines

On 07/09/2009 05:30 PM, DJ Delorie wrote: 
You don't want to generate an error here, because the user does
not control all possible queries of this function.


Fixed.  However, if the callee is "__inline" (i.e. forced inline),
the target check doesn't override it and it's inlined anyway. That's
one of the cases we're trying to avoid, and error on.

Then that's a bug, and should be fixed.

Also, inline isn't forced inline it's suggested.  Forced inline is
attribute((always_inline)).  And that said we generate errors elsewhere
that always_inline functions can't be inlined, so why not for this one?



r~

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]