public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: michael@fastmail.ca To: gcc-gnats@gcc.gnu.org Subject: other/6218: Build hangs on DS10- OSF1 V4.0 1229 alpha Date: Sun, 07 Apr 2002 13:16:00 -0000 [thread overview] Message-ID: <20020407200817.26530.qmail@sources.redhat.com> (raw) >Number: 6218 >Category: other >Synopsis: Build hangs on DS10- OSF1 V4.0 1229 alpha >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Apr 07 13:16:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: ? >Release: gcc-3.0.4 >Organization: >Environment: Dec-UX v.4.0f Currently installed compiler: Reading specs from /usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95/specs gcc version 2.95 19990728 (release) >Description: The compile of gcc hangs while compiling parse.c for some sort of java part of gcc. The original make tries to build it with -O2 but that was left churning for 14 hours without returning. Original: gcc -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Ijava -I../../gcc -I../../gcc/java -I../../gcc/config -I../../gcc/../include ../../gcc/java/parse.c -o java/parse.o Modified: gcc -c -DIN_GCC -g -O -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Ijava -I../../gcc -I../../gcc/java -I../../gcc/config -I../../gcc/../include ../../gcc/java/parse.c -o java/parse.o The modified one compiles in a reasonable amount of time (20 seconds or so). This problem seems to appear with the stock configure/make without any special options. I was able to get around it by stopping the build, going into the gcc directory, running my modified command with -O instead of -O2 and then going back to my objdir and running make again. -Michael >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-04-07 20:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020407200817.26530.qmail@sources.redhat.com \ --to=michael@fastmail.ca \ --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).