This is the mail archive of the gcc@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: sh-rtems egcs-1.0.2-prerelease 980310



  In message <199803112220.RAA16906@tiktok.cygnus.com>you write:
  > |   In message <199803112137.VAA08403@phal.cygnus.co.uk>you write:
  > |   > > It's silly and braindead to force a port to declare variables like
  > |   > > "optimize".  Your argument makes much more sense if the problem was
  > |   > > a more obscure variable.
  > |   > 
  > |   > Ok.  So how about including flags.h in rtlanal.h ?
  > | For the release branch I just declared optimize in rtlanal.c.
  > |
  > | I don't know how we want to handle this for the mainline
  > | sources.  I'll think about that after I get back.
  > 
  > It would be nice if flags.h were included everywhere.
This would seem fine to me.


  > It would be even
  > nicer if all of those flag_* variables were grouped into a structure (with
Agreed 100%

jeff


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