public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sdack@anitesystems.de
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6591: genrecog: Internal compiler error in `merge_trees' at gcc/genrecog.c:968
Date: Tue, 07 May 2002 06:46:00 -0000	[thread overview]
Message-ID: <20020507133734.12148.qmail@sources.redhat.com> (raw)


>Number:         6591
>Category:       bootstrap
>Synopsis:       genrecog: Internal compiler error in `merge_trees' at gcc/genrecog.c:968
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 06:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Sven Dack
>Release:        gcc-2.95.3
>Organization:
>Environment:
m88k-motorola-sysv4
>Description:
Building gcc-2.95.3 fails after stage1/xgcc has been build. Make aborts with:

stage1/xgcc -Bstage1 -B/MCM/gnu/m88k-motorola-sysv4/bin/ -DIN_GCC -DNO_BUGS -D__STDC__=0 -O -DHAVE_CONFIG_H -o genrecog genrecog.o rtl.o bitmap.o print-rtl.o ... (with obstack.o and alloca.a as it seems)
./genrecog ../../gcc-2.95.3/gcc/config/m88k/m88k.md > tmp-recog.c
genrecog: Internal compiler error in `merge_trees' at .../gcc/genrecog.c:968
Pleas submit a full bug report (hope that's full enough).
See <URL...>
after 31 definitions

The genrecog previous to that did not fail. I will try with other options some other time.
>How-To-Repeat:
mkdir objdir; cd objdir
../gcc-2.95.3/configure --prefix=/MCM/gnu --enable-lanuages=c
gmake CFLAGS="-O" LIBCFLAGS="-O" BOOT_CFLAGS="-O2" bootstrap
>Fix:

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


                 reply	other threads:[~2002-05-07 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=20020507133734.12148.qmail@sources.redhat.com \
    --to=sdack@anitesystems.de \
    --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).