public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54142] New: ppc64 build failure - Unrecognized opcode: `sldi' (and `srdi`)
Date: Tue, 31 Jul 2012 15:35:00 -0000 [thread overview]
Message-ID: <bug-54142-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54142
Bug #: 54142
Summary: ppc64 build failure - Unrecognized opcode: `sldi' (and
`srdi`)
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: gary@intrepid.com
Target: powerpc64
On several PPC64 systems, we are seeing the following build failure.
/home/garyf/gcc-4.8/wrk/./gcc/xgcc -B/home/garyf/gcc-4.8/wrk/./gcc/
[...]
-I/home/garyf/gcc-4.8/src/libgcc/../libdecnumber -DHAVE_CC_TLS -o
_gcov_execle.o -MT _g
cov_execle.o -MD -MP -MF _gcov_execle.dep -DL_gcov_execle -c /home/garyf/gcc-4.
8/src/libgcc/libgcov.c
/tmp/ccqVYRai.s: Assembler messages:
/tmp/ccqVYRai.s:63: Error: Unrecognized opcode: `sldi'
/tmp/ccqVYRai.s:66: Error: Unrecognized opcode: `srdi'
/tmp/ccqVYRai.s:67: Error: Unrecognized opcode: `sldi'
/tmp/ccqVYRai.s:73: Error: Unrecognized opcode: `srdi'
/tmp/ccqVYRai.s:74: Error: Unrecognized opcode: `sldi'
/tmp/ccqVYRai.s:88: Error: Unrecognized opcode: `sldi'
The failures above use the gcc-4.8-20120729 snapshot which is based on svn
revision 189947.
The configure target is: powerpc64-unknown-linux-gnu
This was built on a rather old (FC6) system running on a Mac G5, but we have
seen it also fail on newer PPC64 systems.
next reply other threads:[~2012-07-31 15:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:35 gary at intrepid dot com [this message]
2012-07-31 16:12 ` [Bug target/54142] " gary at intrepid dot com
2012-07-31 16:35 ` pinskia at gcc dot gnu.org
2012-07-31 16:54 ` gary at intrepid dot com
2012-07-31 16:58 ` gary at intrepid dot com
2012-07-31 17:14 ` gary at intrepid dot com
2012-07-31 17:59 ` PHHargrove at lbl dot gov
2012-08-11 1:24 ` gary at intrepid dot com
2012-08-13 22:04 ` PHHargrove at lbl dot gov
2012-08-13 22:42 ` PHHargrove at lbl dot gov
2012-08-13 22:54 ` PHHargrove at lbl dot gov
2012-08-13 23:01 ` gary at intrepid dot com
2012-08-13 23:14 ` [Bug target/54142] [4.8 regression] " schwab@linux-m68k.org
2012-08-14 0:01 ` PHHargrove at lbl dot gov
2012-08-14 7:49 ` jakub at gcc dot gnu.org
2012-08-14 13:17 ` gary at intrepid dot com
2012-08-14 16:45 ` segher at gcc dot gnu.org
2012-08-14 17:11 ` dje at gcc dot gnu.org
2012-08-14 22:55 ` segher at gcc dot gnu.org
2012-08-16 0:59 ` segher at gcc dot gnu.org
2012-08-16 2:18 ` segher at gcc dot gnu.org
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=bug-54142-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).