public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@stanford.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/3076: gcc 2.96 (or 3.0) -ANSI does not work right Date: Thu, 07 Jun 2001 16:36:00 -0000 [thread overview] Message-ID: <20010607233601.8654.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/3076; it has been noted by GNATS. From: "Zack Weinberg" <zackw@stanford.edu> To: tony_hsu@amdahl.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/3076: gcc 2.96 (or 3.0) -ANSI does not work right Date: Thu, 7 Jun 2001 16:34:35 -0700 On Thu, Jun 07, 2001 at 05:55:18PM -0000, tony_hsu@amdahl.com wrote: > >Synopsis: gcc 2.96 (or 3.0) -ANSI does not work right ... > $ gcc -ANSI t.c > > Under 2.96 + RedHat7.0 + Intel PIII > Internal error: Segmentation fault (program cpp0) > > Under CodeSourcery's OnLine TestCompilation > : missing '(' after predicate GCC's command line options are case sensitive. The option you are trying to use is spelled -ansi; however, we encourage the use of the -std option instead (-std=c89 for the 1989 C standard, -std=c99 for the 1999 revision). -ANSI is interpreted as a use of the -A option with an invalid argument. "missing '(' after predicate" is a correct, although unhelpful, error message. Red Hat's 2.96 crashes because of a bug that was fixed a long time ago in the official source tree. GCC 3.0 (as you saw from the online test compilation form) will not crash. 2.95.x also does not crash. You should report this crash to Red Hat; we cannot fix bugs in their version of the compiler. [Could someone please close this bug report? I do not have GNATS write privileges.] zw
next reply other threads:[~2001-06-07 16:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-07 16:36 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-07 23:09 neil 2001-06-07 10:56 tony_hsu
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010607233601.8654.qmail@sourceware.cygnus.com \ --to=zackw@stanford.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).