public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: gcc-gnats@gcc.gnu.org Subject: bootstrap/10472: [3.4] [cygwin] mainline broken again since 20030413 Date: Wed, 23 Apr 2003 23:06:00 -0000 [thread overview] Message-ID: <20030423230542.26653.qmail@sources.redhat.com> (raw) >Number: 10472 >Category: bootstrap >Synopsis: [3.4] [cygwin] mainline broken again since 20030413 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Apr 23 23:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Giovanni Bajo >Release: unknown-1.0 >Organization: >Environment: i686-pc-cygwin >Description: Mainline is broken again on cygwin. I have a succesfully built compiler dated 20030413. Then, I tried in the last 3-4 days but there is no way to complete a bootstrap succesfully anymore. It dies on stage2: ../stage1/xgcc.exe -B../stage1/ -B/usr/local/i686-pc-cygwin/bin/ -c -DIN_GCC -DL OCALEDIR=\"/usr/local/share/locale\" -DLOCALE_ALIAS_PATH=\"/usr/local/share/loca le\" -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../../../gcc/gcc/int l -I../../../gcc/gcc -I../../../gcc/gcc/config -I../../../gcc/gcc/../include -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Werror -fno-common ../../../gcc/gcc/intl/dcigettext.c -o dcig ettext.o ../../../gcc/gcc/intl/dcigettext.c: In function `dcigettext__': ../../../gcc/gcc/intl/dcigettext.c:677: internal compiler error: in instantiate_ virtual_regs_lossage, at function.c:3820 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. It's configured with ../gcc/configure --enable-languages=c,c++ --program-suffix=-3.4 --enable-threads=posix Should I submit a preprocessed source for that file? >How-To-Repeat: Download and try to bootstrap mainline on cygwin >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-23 23:06 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=20030423230542.26653.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --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).