public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/12527] New: [3.4 regression] [arm] bootstrap error on arm-linux Date: Mon, 06 Oct 2003 20:03:00 -0000 [thread overview] Message-ID: <20031006200259.12527.debian-gcc@lists.debian.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12527 Summary: [3.4 regression] [arm] bootstrap error on arm-linux Product: gcc Version: 3.3.2 Status: UNCONFIRMED Severity: critical Priority: P2 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: arm-linux GCC host triplet: arm-linux GCC target triplet: arm-linux seen on HEAD 20031005 and 20030909, last sucessful bootstrap on HEAD 20030722. stage1/xgcc -Bstage1/ -B/usr/lib/gcc-snapshot/arm-linux/bin/ -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o genconstants \ genconstants.o gensupport.o dummy-conditions.o rtl.o read-rtl.o bitmap.o ggc-none.o \ errors.o ../libiberty/libiberty.a ./genconstants ../../src/gcc/config/arm/arm.md > tmp-constants.h make[4]: *** [s-constants] Error 132
next reply other threads:[~2003-10-06 20:03 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-06 20:03 debian-gcc at lists dot debian dot org [this message] 2003-10-09 1:43 ` [Bug target/12527] " pinskia at gcc dot gnu dot org 2003-10-11 3:32 ` [Bug target/12527] [3.4 regression] [arm] bootstrap error on arm-linux, miscompiling genconstants pinskia at gcc dot gnu dot org 2003-10-11 11:34 ` doko at cs dot tu-berlin dot de 2003-10-11 12:06 ` rearnsha at gcc dot gnu dot org 2003-10-12 7:24 ` doko at cs dot tu-berlin dot de 2003-10-13 12:41 ` rearnsha at gcc dot gnu dot org 2003-10-13 20:56 ` doko at cs dot tu-berlin dot de 2003-10-14 4:10 ` pinskia at gcc dot gnu dot org 2003-10-14 6:51 ` doko at cs dot tu-berlin dot de 2003-10-14 9:52 ` rearnsha at gcc dot gnu dot org 2003-10-14 20:49 ` debian-gcc at lists dot debian dot org 2003-10-15 13:30 ` rearnsha at gcc dot gnu dot org 2003-10-15 14:30 ` rearnsha at gcc dot gnu dot org 2003-12-21 3:28 ` steven at gcc dot gnu dot org 2004-01-10 22:49 ` pinskia at gcc dot gnu dot org 2004-01-12 16:12 ` [Bug bootstrap/12527] " rearnsha at gcc dot gnu dot org 2004-01-12 16:18 ` pinskia at gcc dot gnu dot org 2004-01-12 17:05 ` bangerth at dealii dot org 2004-01-14 9:18 ` steven at gcc dot gnu dot org 2004-01-14 9:26 ` rearnsha at arm dot com 2004-01-14 17:51 ` cvs-commit at gcc dot gnu dot org 2004-01-14 17:56 ` rearnsha at gcc dot gnu dot org 2004-01-27 13:08 ` cvs-commit at gcc dot gnu dot org 2004-03-30 20:44 ` cvs-commit at gcc dot gnu dot org 2004-03-30 21:17 ` [Bug bootstrap/12527] [3.3/3.4 " pinskia at gcc dot gnu dot org 2005-08-14 18:53 ` buytenh at wantstofly dot org 2005-08-15 9:37 ` rearnsha at gcc dot gnu dot org
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=20031006200259.12527.debian-gcc@lists.debian.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).