This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/10777: gcc: unrecognized option `-no-cpp-precomp'
- From: shrao at nyx dot net
- To: gcc-gnats at gcc dot gnu dot org
- Cc: mark at codesourcery dot com
- Date: 14 May 2003 06:27:52 -0000
- Subject: other/10777: gcc: unrecognized option `-no-cpp-precomp'
- Reply-to: shrao at nyx dot net
>Number: 10777
>Category: other
>Synopsis: gcc: unrecognized option `-no-cpp-precomp'
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed May 14 06:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Shrisha Rao
>Release: gcc 3.3-prerelease
>Organization:
>Environment:
MacOS X 10.2.6 (Darwin 6.6)
>Description:
When gcc 3.3 is compiled using Apple's gcc 3.1 (December 2002 Developer Tools) it compiles fine with just the usual warnings. But when it is bootstrapped using itself (i.e., using a gcc 3.3 compiled from Apple's gcc), there is the odd warning message which repeats as often as the flag is used:
gcc: unrecognized option `-no-cpp-precomp'
One example:
gcc -g -no-cpp-precomp -DHAVE_DESIGNATED_INITIALIZERS=0 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc-3.3/gcc/gcc -I../../gcc-3.3/gcc/gcc/. -I../../gcc-3.3/gcc/gcc/config -I../../gcc-3.3/gcc/gcc/../include -c insn-recog.c \
-o insn-recog.o
gcc: unrecognized option `-no-cpp-precomp'
The bootstrap does run to completion nonetheless, and there are no tangible consequences of this warning that I have been able to find. It still is a wonder why gcc 3.3 does not have -no-cpp-precomp enabled.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: