public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: joel@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Subject: bootstrap/9772: [d30v-elf] fails to build on 3.4 branch -- regression Date: Thu, 20 Feb 2003 13:46:00 -0000 [thread overview] Message-ID: <20030220133908.2787.qmail@sources.redhat.com> (raw) >Number: 9772 >Category: bootstrap >Synopsis: [d30v-elf] fails to build on 3.4 branch -- regression >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Feb 20 13:46:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: joel@gcc.gnu.org >Release: 3.4 branch >Organization: >Environment: RedHat GNU/Linux 7.3, binutils 2.13.2.1, newlib 1.11.0, gcc 3.4 branch >Description: The build fails in the cross build of libiberty which is worse than 3.3 which could at least complete a build of a C-only toolset. The build fails with: /opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-d30v-elf/gcc/xgcc -B/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-d30v-elf/gcc/ -nostdinc -B/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-d30v-elf/d30v-elf/newlib/ -isystem /opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-d30v-elf/d30v-elf/newlib/targ-include -isystem /opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/gcc-3.3-branch/newlib/libc/include -B/opt/gnucross-test/d30v-elf/bin/ -B/opt/gnucross-test/d30v-elf/lib/ -isystem /opt/gnucross-test/d30v-elf/include -c -DHAVE_CONFIG_H -g -Os -Wa,-C -I. -I../../../gcc-3.3-branch/libiberty/../include -W -Wall -Wtraditional -pedantic ../../../gcc-3.3-branch/libiberty/ternary.c -o ternary.o ../../../gcc-3.3-branch/libiberty/ternary.c: In function `ternary_search': ../../../gcc-3.3-branch/libiberty/ternary.c:145: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-02-20 13:46 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=20030220133908.2787.qmail@sources.redhat.com \ --to=joel@gcc.gnu.org \ --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).