public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: he@marel.is
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/5072: xgcc for fr30 segfaults when building crosscompiler gcc3.0.2
Date: Tue, 11 Dec 2001 04:06:00 -0000	[thread overview]
Message-ID: <20011211120114.18725.qmail@sources.redhat.com> (raw)


>Number:         5072
>Category:       bootstrap
>Synopsis:       xgcc for fr30 segfaults when building crosscompiler gcc3.0.2
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 11 04:06:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     he@marel.is
>Release:        gcc-3.0.2
>Organization:
>Environment:
Vanilla RedHat 7.2
>Description:
When building a cross compiler for fr30 I get an internal error:segfault from xgcc.

/home/he/M3000/build/gcc-fr30/gcc/xgcc -B/home/he/M3000/build/gcc-fr30/gcc/ -B/usr/local/fr30//fr30-unknown-elf/bin/ -B/usr/local/fr30//fr30-unknown-elf/lib/ -isystem /usr/local/fr30//fr30-unknown-elf/include -O2  -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../../src/gcc-3.0.2/gcc -I../../../src/gcc-3.0.2/gcc/. -I../../../src/gcc-3.0.2/gcc/config -I../../../src/gcc-3.0.2/gcc/../include  -DL_divdi3 -c ../../../src/gcc-3.0.2/gcc/libgcc2.c -o libgcc/./_divdi3.o
../../../src/gcc-3.0.2/gcc/libgcc2.c: In function `__divdi3':
../../../src/gcc-3.0.2/gcc/libgcc2.c:748: Internal error: Segmentation fault
Please submit a full bug report,
>How-To-Repeat:
build a gcc crosscompiler for fr30-efl on redhat7.2
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-12-11 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  4:06 he [this message]
2001-12-11 16:00 rodrigc
2001-12-11 16:06 rodrigc

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=20011211120114.18725.qmail@sources.redhat.com \
    --to=he@marel.is \
    --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).