public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tm2@best.com To: gcc-gnats@gcc.gnu.org Subject: bootstrap/3317: GCC-MCORE: compiler for mcore-elf target fails to build Date: Thu, 21 Jun 2001 01:56:00 -0000 [thread overview] Message-ID: <20010621085158.16044.qmail@sourceware.cygnus.com> (raw) >Number: 3317 >Category: bootstrap >Synopsis: GCC-MCORE: compiler for mcore-elf target fails to build >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 21 01:56:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Toshiyasu Morita >Release: 3.0 >Organization: >Environment: host: i686-linux (Red Hat 7.0) target: mcore-elf >Description: Compiler fails to build. Tail of build log below: /home/tm/gcc-3.0-mcore-elf/gcc/xgcc -B/home/tm/gcc-3.0-mcore-elf/gcc/ -B/usr/local/mcore-elf/bin/ -B/usr/local/mcore-elf/lib/ -isystem /usr/local/mcore-elf/include -O2 -DCROSS_COMPILE -DIN_GCC -DDONT_HAVE_STDIO -DDONT_HAVE_SETJMP -Dinhibit_libc -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -O3 -DNO_FLOATLIB_FIXUNSDFSI -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include -DL_subvsi3 -c ../../gcc/gcc/libgcc2.c -o libgcc/./_subvsi3.o ../../gcc/gcc/libgcc2.c: In function `__subvsi3': ../../gcc/gcc/libgcc2.c:109: warning: implicit declaration of function `abort' ../../gcc/gcc/libgcc2.c:106: Internal compiler error in gen_rtx_SUBREG, at emit-rtl.c:362 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: ../gcc-3.0/configure --target=mcore-elf ; make >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-21 1:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-21 1:56 tm2 [this message] 2002-03-27 12:16 law
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=20010621085158.16044.qmail@sourceware.cygnus.com \ --to=tm2@best.com \ --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).