public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "PHHargrove at lbl dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54142] ppc64 build failure - Unrecognized opcode: `sldi' (and `srdi`)
Date: Mon, 13 Aug 2012 22:04:00 -0000 [thread overview]
Message-ID: <bug-54142-4-UvxMrA33Pp@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 #8 from Paul H. Hargrove <PHHargrove at lbl dot gov> 2012-08-13 22:04:40 UTC ---
The following is a transcript of a test I just tried one of my systems where
Gary and I have observed this bug. The test appears to show that the gcc
provided by Fedora Core 6 does generate "sldi" instructions and the
system-provided assembler understands them. So, whatever is causing the build
failures that Gary and I see, it is *not* simply a matter of an assembler not
supporting the instructions.
-Paul
{phargrov@fc6 ~}$ cat q.c
unsigned long long foo(void) { return 0x00007FFF00000000LLU; }
{phargrov@fc6 ~}$ gcc -m64 -O -S q.c
{phargrov@fc6 ~}$ cat q.s
.file "q.c"
.section ".toc","aw"
.section ".text"
.align 2
.globl foo
.section ".opd","aw"
.align 3
foo:
.quad .L.foo,.TOC.@tocbase
.previous
.type foo, @function
.L.foo:
lis 3,0x7fff
sldi 3,3,16
blr
.long 0
.byte 0,0,0,0,0,0,0,0
.size foo,.-.L.foo
.ident "GCC: (GNU) 4.1.2 20070626 (Red Hat 4.1.2-13)"
.section .note.GNU-stack,"",@progbits
{phargrov@fc6 ~}$ as -a64 -mppc64 q.s
[no errors]
next prev parent reply other threads:[~2012-08-13 22:04 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
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 [this message]
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-UvxMrA33Pp@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).