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]

Re: __INLINING__ patch



  In message <14458.28181.470249.555700@casey.transmeta.com>you write:
  >  > Similar changes also need to be installed into the language specific
  >  > drivers since C isn't the only language that can/should be able to use
  >  > this information.  Probably the quickest way to find the locations that
  >  > need updating is to grep OPTIMIZE */*specs*.
  > 
  > Maybe we can turn this around and say it's -fno-inline that is causing
  > the problems.  That's easy to key off of in specs files.  So how about
  > define __FOO__ if -fno-inline is specified, ignoring the value of -On
  > [you pick "FOO" so we avoid a round of "but SUCH_AND_SUCH is
  > ambiguous". :-) A straightforward example is __FNO_INLINE__.]
  > Would that work?
Sounds reasonable to me.  How about __FLAG_NO_INLINE__ for this purpose?  

jeff



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