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] ppc64 build failure - Unrecognized opcode: `sldi' (and `srdi`)
Date: Tue, 31 Jul 2012 17:14:00 -0000 [thread overview]
Message-ID: <bug-54142-4-eRp92dQAE4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54142-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54142
--- Comment #5 from Gary Funck <gary at intrepid dot com> 2012-07-31 17:14:24 UTC ---
Here is the complete output at the point of a make failure.
/home/garyf/gcc-4.8/wrk/./gcc/xgcc -B/home/garyf/gcc-4.8/wrk/./gcc/ -B/home/gar
yf/gcc-4.8/rls/powerpc64-unknown-linux-gnu/bin/ -B/home/garyf/gcc-4.8/rls/power
pc64-unknown-linux-gnu/lib/ -isystem /home/garyf/gcc-4.8/rls/powerpc64-unknown-
linux-gnu/include -isystem /home/garyf/gcc-4.8/rls/powerpc64-unknown-linux-gnu/
sys-include -O2 -O0 -g3 -O2 -O2 -O0 -g3 -DIN_GCC -W -Wall -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -
isystem ./include -fPIC -mlong-double-128 -mno-minimal-toc -g -DIN_LIBGCC2 -f
building-libgcc -fno-stack-protector -fPIC -mlong-double-128 -mno-minimal-toc
-I. -I. -I../.././gcc -I/home/garyf/gcc-4.8/src/libgcc -I/home/garyf/gcc-4.8/s
rc/libgcc/. -I/home/garyf/gcc-4.8/src/libgcc/../gcc -I/home/garyf/gcc-4.8/src/l
ibgcc/../include -I/home/garyf/gcc-4.8/src/libgcc/../libdecnumber/dpd -I/home/g
aryf/gcc-4.8/src/libgcc/../libdecnumber -DHAVE_CC_TLS -o _mulvdi3.o -MT _mulvd
i3.o -MD -MP -MF _mulvdi3.dep -DL_mulvdi3 -c /home/garyf/gcc-4.8/src/libgcc/lib
gcc2.c -fvisibility=hidden -DHIDE_EXPORTS
/tmp/cci4OPcY.s: Assembler messages:
/tmp/cci4OPcY.s:384: Error: Unrecognized opcode: `srdi'
/tmp/cci4OPcY.s:430: Error: Unrecognized opcode: `srdi'
/tmp/cci4OPcY.s:481: Error: Unrecognized opcode: `srdi'
/tmp/cci4OPcY.s:535: Error: Unrecognized opcode: `srdi'
next prev parent reply other threads:[~2012-07-31 17:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:35 [Bug target/54142] New: " gary at intrepid dot com
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 [this message]
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-eRp92dQAE4@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).