This is the mail archive of the
mailing list for the GCC project.
Re: PATCH (trunk rev.119231): ability to disable an option at configure time
On Sun, Nov 26, 2006 at 02:56:30PM -0800, Andrew Pinski wrote:
> In fact the reason why we have options in general is to disable
> expensive processing and not configure options. Now defaulting to
> on/off is a different story but fully disabling an option seems wrong.
I agree; I don't think we should be making this distinction. If an
option isn't compiled in for some reason (e.g. because an external
library was missing), we should still recognize the option so that we
can give a sensible error message.