public inbox for
help / color / mirror / Atom feed
Subject: other/10777: gcc: unrecognized option `-no-cpp-precomp'
Date: Wed, 14 May 2003 06:36:00 -0000	[thread overview]
Message-ID: <> (raw)

>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
>Originator:     Shrisha Rao
>Release:        gcc 3.3-prerelease
MacOS X 10.2.6 (Darwin 6.6)
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.



             reply	other threads:[~2003-05-14  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  6:36 shrao [this message]
2003-05-14  7:36 Dara Hazeghi
2003-05-14 12:06 Andrew Pinski
2003-05-14 14:10 bangerth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).