[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
--- Comment #7 from jsm28 at gcc dot gnu dot org 2010-05-28 17:29 --- Subject: Bug 15303 Author: jsm28 Date: Fri May 28 17:28:57 2010 New Revision: 159986 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=159986 Log: PR driver/15303 * gcc.c (inform, warning, inform): New functions. (fatal_ice): Rename to internal_error; change cmsgid parameter to gmsgid. All callers changed. (notice): Rename to fnotice; add parameter fp. All callers changed. (fatal_error): Rename to fatal_signal. All users changed. (fatal): Rename to fatal_error; change cmsgid parameter to gmsgid. All callers changed. (process_command): Use warning instead of error for warnings. (end_going_arg): Don't use _() around argument of error. (do_spec_1): Use inform for message from %n specs. Use warning instead of error for warnings. (main): Use inform for comparison messages. Use warning for message about unused linker input. (error): Increment error_count. Print error: . * gcc.h (fatal): Change to fatal_error. (warning): Declare. * config/darwin-driver.c (darwin_default_min_version): Use warning instead of fprintf for warnings. * cppspec.c (lang_specific_driver): Use fatal_error instead of fatal. cp: * g++spec.c (lang_specific_driver): Use fatal_error instead of fatal. fortran: * gfortranspec.c (append_arg, lang_specific_driver): Use fatal_error instead of fatal. Use warning instead of fprintf for warnings. java: * jvspec.c (lang_specific_driver): Use fatal_error instead of fatal. Use warning instead of error for warnings. Modified: trunk/gcc/ChangeLog trunk/gcc/config/darwin-driver.c trunk/gcc/cp/ChangeLog trunk/gcc/cp/g++spec.c trunk/gcc/cppspec.c trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortranspec.c trunk/gcc/gcc.c trunk/gcc/gcc.h trunk/gcc/java/ChangeLog trunk/gcc/java/jvspec.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303
[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
--- Comment #8 from jsm28 at gcc dot gnu dot org 2010-05-28 17:29 --- Fixed for 4.6. -- jsm28 at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Known to work||4.6.0 Resolution||FIXED Target Milestone|--- |4.6.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303
[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
--- Comment #6 from tromey at gcc dot gnu dot org 2007-01-22 04:16 --- The fix is simple -- change a single error() to a fatal(). I'll submit this after running the test suite. -- tromey at gcc dot gnu dot org changed: What|Removed |Added CC||tromey at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303
[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
--- Comment #4 from davida at pobox dot com 2006-03-27 01:30 --- As a specific example, using autoconf to attempt to portably determine whether to use -pthreads (Solaris) or -pthread (Linux, etc) to request reentrant libraries and thread library linkage, gcc will warn, but otherwise accept, the wrong flag. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303
[Bug driver/15303] When gcc sees an unrecognized option, the exit status indicates success
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-03-27 01:32 --- (In reply to comment #4) As a specific example, using autoconf to attempt to portably determine whether to use -pthreads (Solaris) or -pthread (Linux, etc) to request reentrant libraries and thread library linkage, gcc will warn, but otherwise accept, the wrong flag. That does not matter any more in 4.1.0 and above :). as -pthread is good on Solaris as also on Linux. Also you can look at the output of the compiler instead of depending on the return value :). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303