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: Tue, 31 Jul 2012 17:59:00 -0000	[thread overview]
Message-ID: <bug-54142-4-49W0O8EEkZ@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 #6 from Paul H. Hargrove <PHHargrove at lbl dot gov> 2012-07-31 17:59:31 UTC ---
(In reply to comment #2)
> sldi and srdi are both standard PowerPC64 instructions.


IBM's "Programming Environments Manual for 64-Bit Microprocessors" lists sldi
and srdi as "Simplified Mnemonics".  Perhaps using the canonical instructions
is a simple resolution to this bug?

Shift left immediate      sldi rA,rS,n (n < 64)        rldicr rA,rS,n,63 – n
Shift right immediate    srdi rA,rS,n (n < 64)        rldicl rA,rS,64 – n,n


Additionally, there may be a GAS bug lurking here as well.


  parent reply	other threads:[~2012-07-31 17:59 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 [this message]
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-49W0O8EEkZ@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).