public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: smarks@mobile-mind.com
To: gcc-gnats@gcc.gnu.org
Subject: c/6359: Internal compiler error building dev for target=FR30
Date: Thu, 18 Apr 2002 07:56:00 -0000 [thread overview]
Message-ID: <20020418144944.5439.qmail@sources.redhat.com> (raw)
>Number: 6359
>Category: c
>Synopsis: Internal compiler error building dev for target=FR30
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 18 07:56:03 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Scott Marks
>Release: unknown-1.0
>Organization:
>Environment:
WinXP - Cygwin loaded with root C:\cygwin - no Visual Studio - binutils built
>Description:
Built binutils in /usr/local/src/... with --target=fr30-fujitsu-elf, no problem. Today's (2002-04-18) CVS snapshot in /usr/local/gcc..., ran ./configure --target=fr30-fujitsu-elf, no problem. Ran make LANGUAGES=c, compiling dp-bit.c to produce _addsub_df.o, got:
dp-bit.c: In function `_fpadd_parts':
dp-bit.c:561: Internal compiler error in change_address_1, at emit-rtl.c:1784
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [libgcc/./_addsub_df.o] Error 1
make[2]: Leaving directory `/usr/local/gcc/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/usr/local/gcc/gcc'
make: *** [all-gcc] Error 2
>How-To-Repeat:
Install cygwin, download binutils from sources.redhat.com, configure binutils and friends using --target=fr30-*-elf, build, download gcc from gcc.gnu.org, configure simlarly, make LANGUAGES=c.
>Fix:
None known.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-18 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 7:56 smarks [this message]
2002-04-18 10:14 hp
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=20020418144944.5439.qmail@sources.redhat.com \
--to=smarks@mobile-mind.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: link
Be 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).