public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Anthony Green <green@cygnus.com> To: gcc-gnats@gcc.gnu.org Subject: c++/3240: sh-elf libstdc++-v3 does not build Date: Mon, 18 Jun 2001 13:16:00 -0000 [thread overview] Message-ID: <200106182013.NAA22653@fencer.cygnus.com> (raw) >Number: 3240 >Category: c++ >Synopsis: sh-elf libstdc++-v3 does not build >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Jun 18 13:16:03 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Anthony Green >Release: 3.1 20010617 (experimental) >Organization: >Environment: System: Linux fencer.cygnus.com 2.2.12-20smp #1 SMP Mon Sep 27 10:34:45 EDT 1999 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: sh-unknown-elf configured with: /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/configure --prefix=/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/install --program-prefix=sh-elf- --target=sh-elf --with-gnu-as --with-gnu-ld >Description: Building gcc for sh-elf results in... /horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/gcc/xgcc -B/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/gcc/ -nostdinc++ -L/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/sh-elf/ml/m3e/libstdc++-v3/src -L/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/sh-elf/ml/m3e/libstdc++-v3/src/.libs -nostdinc -B/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/sh-elf/ml/m3e/newlib/ -isystem /horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/build-gcc/sh-elf/ml/m3e/newlib/targ-include -isystem /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/newlib/libc/include -B/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/install/sh-elf/bin/ -B/horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/install/sh-elf/lib/ -isystem /horton/green/gcj-test/2001-06-17-18.45.14/sh-elf/install/sh-elf/include -ml -m3e -nostdinc++ -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/include -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/! libstdc++-v3/include/std -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/include/c_std -I../include -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/libsupc++ -I../libio -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/libio -I/horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/libmath -g -O2 -ml -m3e -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/src/complex_io.cc -o complex_io.o /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/include/bits/std_complex.h: In function `std::basic_istream<_CharT, _Traits>& std::operator>>(std::basic_istream<_CharT, _Traits>&, std::complex<_Tp>&) [with _Tp = float, _CharT = char, _Traits = std::char_traits<char>]': /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/src/complex_io.cc:36: instantiated from here /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/include/bits/std_complex.h:375: Unrecognizable insn: (insn 157 156 158 (parallel[ (set (mem/s:SF (plus:SI (reg/v/u/f:SI 56) (const_int 4 [0x4])) 0) (reg:SF 92)) (use (reg/v:PSI 48 fpscr)) (clobber (scratch:SI)) ] ) -1 (insn_list 156 (nil)) (expr_list:REG_DEAD (reg:SF 92) (expr_list:REG_DEAD (reg/v/u/f:SI 56) (expr_list:REG_UNUSED (scratch:SI) (nil))))) /horton/green/gcj-test/2001-06-17-18.45.14/gcc/gcc/libstdc++-v3/include/bits/std_complex.h:375: Internal compiler error in extract_insn, at recog.c:2173 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: Check out the latest gcc code, configure for sh-elf and build. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-06-18 13: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=200106182013.NAA22653@fencer.cygnus.com \ --to=green@cygnus.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).