public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wharms@bfs.de To: gcc-gnats@gcc.gnu.org Subject: c/7657: gcc.2.95.2 -O2 (for alpha) loops endless in java/parse.c Date: Tue, 20 Aug 2002 09:06:00 -0000 [thread overview] Message-ID: <20020820160235.25468.qmail@sources.redhat.com> (raw) >Number: 7657 >Category: c >Synopsis: gcc.2.95.2 -O2 (for alpha) loops endless in java/parse.c >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Aug 20 09:06:05 PDT 2002 >Closed-Date: >Last-Modified: >Originator: wharms@bfs.de >Release: unknown-1.0 >Organization: >Environment: linux.2.2.12 gcc version 2.95.2 compiling gcc-3.2 >Description: gcc2.95 has a problem with java/parse.c compiling with option -O2 causes cc1 to loop. removing -O2 solved the problem (for me) /* original */ gcc -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing -prototypes -DHAVE_CONFIG_H -I. -Ijava -I. -I./java -I./config -I./../inclu de java/parse.c -o java/parse.o >How-To-Repeat: >Fix: remove the -O2 for parse.o in the makefile maybe somebody can patch 2.95 because the version is often used. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-20 16:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-20 9:06 wharms [this message] 2002-08-20 10:36 Andrew Pinski 2002-08-26 5:56 jsm28
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=20020820160235.25468.qmail@sources.redhat.com \ --to=wharms@bfs.de \ --cc=gcc-gnats@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).