This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
- From: "ian at wasabisystems dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 May 2004 14:36:36 -0000
- Subject: [Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
- References: <20040506005932.15303.ian@wasabisystems.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ian at wasabisystems dot com 2004-05-06 14:36 -------
Subject: Re: When gcc sees an unrecognized option, the exit status indicates success
"pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-05-06 04:51 -------
> Confirmed, but I think this is so that some options which have an effect on some target's
> native compiler it will not cause gcc to fail. An example of this is -no-cpp-precomp on
> Darwin where Apple's GCC accepts it without an error but the FSF warnings about the
> option but does not fail, if it did then it will cause a bootstrap failure right now on the
> mainline of the FSF's GCC.
I don't think this is a very good reason.
For cases where we want gcc to accept a native compiler option, I
think we should implement that, perhaps using DRIVER_SELF_SPECS,
rather than implementing the general case of accepting all options.
As far as building gcc goes, we should be able to clearly separate
options which we pass to the native compiler and options which we pass
to gcc. For an example of setting host specific compiler options, see
tentative_cc in the top level configure.in file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303