public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pthomas@suse.de
To: gcc-gnats@gcc.gnu.org
Cc: aj@suse.de, dje@watson.ibm.com
Subject: target/5736: bootstraping CVS HEAD on powerpc fails in checked build
Date: Wed, 20 Feb 2002 09:26:00 -0000 [thread overview]
Message-ID: <20020220171441.21050.qmail@sources.redhat.com> (raw)
>Number: 5736
>Category: target
>Synopsis: bootstraping CVS HEAD on powerpc fails in checked build
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 20 09:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: pthomas@suse.de
>Release: 3.1 20020220
>Organization:
>Environment:
powerpc-suse-linux-gnu
gcc configured with:
--enable-shared --with-system-zlib --enable-threads --host=powerpc-suse-linux-gnu --target=powerpc-suse-linux-gnu --build=powerpc-suse-linux-gnu --enable-checking=misc,tree,rtl,gc,gcac
Thread model: posix
>Description:
Bootstrapping CVS HEAD with -O2 fails when compiling libgcc2, specifically _negdi2 with
cc1: RTL check: expected code `const_int', have `plus' in rs6000_legitimate_address, at config/rs6000/rs6000.c:2014
Compiling at lower optimisation succeeds.
>How-To-Repeat:
Compile attatched _negdi2.i with:
./xgcc -B./ -O2 -DIN_GCC -fPIC -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fPIC -mstrict-align -DL_negdi2 -c _negdi2.i
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="_negdi2.i"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="_negdi2.i"
dHlwZWRlZiBpbnQgU0l0eXBlIF9fYXR0cmlidXRlX18gKChtb2RlIChTSSkpKTsKdHlwZWRlZiB1
bnNpZ25lZCBpbnQgVVNJdHlwZSBfX2F0dHJpYnV0ZV9fICgobW9kZSAoU0kpKSk7CgpzdHJ1Y3Qg
RFdzdHJ1Y3Qge1NJdHlwZSBoaWdoLCBsb3c7fTsKCnR5cGVkZWYgdW5pb24KewogIHN0cnVjdCBE
V3N0cnVjdCBzOwogIERJdHlwZSBsbDsKfSBEV3VuaW9uOwoKREl0eXBlCl9fbmVnZGkyIChESXR5
cGUgdSkKewogIERXdW5pb24gdzsKICBEV3VuaW9uIHV1OwoKICB1dS5sbCA9IHU7CgogIHcucy5s
b3cgPSAtdXUucy5sb3c7CiAgdy5zLmhpZ2ggPSAtdXUucy5oaWdoIC0gKChVU0l0eXBlKSB3LnMu
bG93ID4gMCk7CgogIHJldHVybiB3LmxsOwp9Cg==
next reply other threads:[~2002-02-20 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 9:26 pthomas [this message]
2002-02-20 9:56 Graham Stott
2002-02-20 9:56 David Edelsohn
2002-02-20 10:06 Alan Matsuoka
2002-02-20 10:06 Franz Sirl
2002-02-20 10:06 David Edelsohn
2002-02-20 10:06 David Edelsohn
2002-02-20 10:26 Alan Matsuoka
2002-02-20 13:40 Graham Stott
2002-03-13 14:13 dje
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=20020220171441.21050.qmail@sources.redhat.com \
--to=pthomas@suse.de \
--cc=aj@suse.de \
--cc=dje@watson.ibm.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).