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]
Other format: [Raw text]

Re: f_options x common.opt


Hello,

> > I am somewhat confused about how to add new options.  There is
> > common.opt and relater machinery, but still there also is f_options
> > array in toplev.c.
> > 
> > So where should the options be added?  Just to common.opt, or to
> > both?  If to both, why would we have such stupidity?  If just to
> > common.opt, why does f_options still exist?
> 
> f_options is used only for -fverbose-asm.  The common.opt format could be
> extended to list variables for which declarations are to be generated (and
> indeed thus get rid of much of the switch code just assigning to such
> variables) so as to obsolete f_options.

OK, I'm working on that.

Zdenek


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