This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [incremental] Patch: FYI: save and restore options and params
- From: Tom Tromey <tromey at redhat dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Cc: "Gcc Patch List" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 29 Jul 2008 10:07:03 -0600
- Subject: Re: [incremental] Patch: FYI: save and restore options and params
- References: <m3iqzbooww.fsf@fleche.redhat.com> <6c33472e0803242353p29aac946h1207c37fc44df9ec@mail.gmail.com> <m3skyelw0e.fsf@fleche.redhat.com> <6c33472e0807290817j706b07o82945ab9c7d2a58@mail.gmail.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Manuel" == Manuel LÃpez-IbÃÃez <lopezibanez@gmail.com> writes:
Manuel> First, I don't think there is a real reason for any option to not be
Manuel> handled through entries in the *.opt files. It looks like an
Manuel> unfinished transition.
Yeah, I tend to agree, though I have not looked at this in detail.
Manuel> Second, the default value given in the *.opt files through Init()
Manuel> should be stored in your structure default_values. Then, options
Manuel> variables are initialized to some special value UNINITIALIZED.
This only works for variables which cannot take the whole range of
their type. So, I wonder whether it is a general-enough solution.
I'm curious: what is it about this patch that you think would be
worthwhile for trunk?
Anyway, feel free to pick it up. I'm pretty sure I won't be looking
at this patch for quite some time.
Tom