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:42:00 -0000 [thread overview] Message-ID: <bug-54142-4-EApL1MQfnd@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 #9 from Paul H. Hargrove <PHHargrove at lbl dot gov> 2012-08-13 22:42:16 UTC --- Following up on my previous experiment, I tried the same input with the xgcc which is failing to build libdecnumber. If also fails with the 1-line test case: {phargrov@fc6 ~}$ cat q.c unsigned long long foo(void) { return 0x00007FFF00000000LLU; } {phargrov@fc6 ~}$ /usr/local/upc/compiler/bld/./gcc/xgcc -B/usr/local/upc/compiler/bld/./gcc/ -m64 -O ~/q.c /tmp/cctmw5wO.s: Assembler messages: /tmp/cctmw5wO.s:14: Error: Unrecognized opcode: `sldi' Examining stderr when "-v" is passed to the two compilers reveals a KEY difference: {phargrov@fc6 ~}$ gcc -m64 -O -v -c q.c 2>&1 | grep -w as as -a64 -mppc64 -many -V -Qy -o q.o /tmp/ccpjKGBl.s {phargrov@fc6 ~}$ /usr/local/upc/compiler/bld/./gcc/xgcc -B/usr/local/upc/compiler/bld/./gcc/ -m64 -O -v -c ~/q.c 2>&1 | grep -w as /usr/local/upc/compiler/bld/./gcc/as -v -a64 -mcom -many -o q.o /tmp/cctEFZq2.s The difference (other than the use of the built-time wrapper script) is "-mppc64" for the Red Hat built gcc-4.2.1 vs "-mcom" for the 4.8.0 snapshot. The following shows that this flag, not the presence of the wrapper script is the origin of the failure: {phargrov@fc6 ~}$ /usr/local/upc/compiler/bld/./gcc/as -a64 -mcom -many -o q.o q.s q.s: Assembler messages: q.s:14: Error: Unrecognized opcode: `sldi' {phargrov@fc6 ~}$ /usr/local/upc/compiler/bld/./gcc/as -a64 -mppc64 -many -o q.o q.s [no error] {phargrov@fc6 ~}$ /usr/bin/as -a64 -mcom -many -o q.o q.s q.s: Assembler messages: q.s:14: Error: Unrecognized opcode: `sldi' {phargrov@fc6 ~}$ /usr/bin/as -a64 -mppc64 -many -o q.o q.s [no error] So, assuming gas is correct in rejecting 'sldi' and 'srdi' in "common" mode the question becomes, "why is gcc by default specifying a target to the assembler which doesn't support the instructions it is generating?" Of course, if 'sldi' and 'slri' ARE supposed to be supported in "common" mode, then this is a binutils bug.
next prev parent reply other threads:[~2012-08-13 22:42 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 2012-08-13 22:42 ` PHHargrove at lbl dot gov [this message] 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-EApL1MQfnd@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: linkBe 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).