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: [RFA] __attribute__((inline_everything)) 2nd try


On May 14, 2003, Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> wrote:

> Ok, thanks - all lookup_attribute() calls deal with warnings only, so I
> suppose I can ignore those. The inlining decision itself is done via
> DECL_UNINLINABLE - I suppose setting this is enough. I'll try.

Make sure to warn if you find this attribute after we already
generated code for the function.

>> I still think the name is ugly ;)

> Me too ;) But I didnt manage to find a better one, yet.

How about inline_barrier or inline_boundary?

They kind of convey the notion that the function itself shouldn't be
inlined, and, in a weaker way (ok, not at all :-), that other
functions are inlined into it.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


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