public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/7208: build of gnatlib failed with SIGILL
Date: Sat, 13 Jul 2002 10:26:00 -0000 [thread overview]
Message-ID: <20020713172602.25492.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/7208; it has been noted by GNATS.
From: Florian Weimer <fw@deneb.enyo.de>
To: adi@thur.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: ada/7208: build of gnatlib failed with SIGILL
Date: Sat, 13 Jul 2002 19:00:37 +0200
adi@thur.de writes:
> System: Linux drcomp 2.4.18 #13 Sun Mar 3 13:22:15 CET 2002 i586 unknown
> Architecture: i586
>
>
> host: i586-pc-linux-gnu
> build: i586-pc-linux-gnu
> target: i586-pc-linux-gnu
> configured with: ../gcc/configure --enable-languages=c,c++,ada --enable-threads --enable-shared
>>Description:
> Compiling s-auxdec.adb causes xgcc to receive SIGILL, afterwards
> leaking much memory which will end in a kill with out-of-memory
> (I've interrupted here interactively)
>
> ../../xgcc -B../../ -c -g -O2 -g -O2 -W -Wall -gnatpg -I. -I/bigspace/build/gcc/gcc/ada s-auxdec.adb
> +===========================GNAT BUG DETECTED==============================+
> | 3.2 20020704 (experimental) (i586-pc-linux-gnu) GCC error: |
> | internal error: Illegal instruction |
I'm sorry, but I can't reproduce this with the current CVS. Do you
still see this problem?
next reply other threads:[~2002-07-13 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 10:26 Florian Weimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 11:58 fw
2002-07-14 3:06 Florian Weimer
2002-07-14 3:06 Adrian Knoth
2002-07-14 1:56 Florian Weimer
2002-07-13 18:06 Adrian Knoth
2002-07-04 11:46 adi
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=20020713172602.25492.qmail@sources.redhat.com \
--to=fw@deneb.enyo.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).