public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106895] powerpc64 strange extended inline asm behaviour with register pairs
Date: Fri, 09 Sep 2022 11:56:07 +0000	[thread overview]
Message-ID: <bug-106895-4-nPX7ifMf4P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106895-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106895

Peter Bergner <bergner at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bergner at gcc dot gnu.org,
                   |                            |meissner at gcc dot gnu.org

--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
Using the type __int128 will give you a register pair, but will not guarantee
an even/odd pair.  The "r" constraint will make sure you have a GPR, but again,
doesn't give you an even register.  Looking through our backend, we seem to use
the wQ constraint internally when generating the stq insn.  You could try that.
Mike, is that the correct thing to use here to get an even/odd GPR pair?

  parent reply	other threads:[~2022-09-09 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 11:25 [Bug c/106895] New: " npiggin at gmail dot com
2022-09-09 11:35 ` [Bug c/106895] " rguenth at gcc dot gnu.org
2022-09-09 11:56 ` bergner at gcc dot gnu.org [this message]
2022-09-13 15:34 ` [Bug target/106895] " segher at gcc dot gnu.org
2023-06-15 10:26 ` npiggin at gmail dot com
2023-06-15 12:59 ` pinskia at gcc dot gnu.org
2023-07-03  4:30 ` [Bug target/106895] powerpc64 unable to specify even/odd register pairs in extended inline asm segher at gcc dot gnu.org
2023-07-03 15:45 ` bergner at gcc dot gnu.org
2023-07-03 16:55 ` schwab@linux-m68k.org
2023-07-04 16:18 ` segher at gcc dot gnu.org
2023-07-06 11:17 ` npiggin at gmail dot com
2023-07-06 13:46 ` segher at gcc dot gnu.org
2023-07-07  0:00 ` npiggin at gmail dot com
2023-07-07 19:31 ` segher at gcc dot gnu.org
2023-07-09  5:06 ` npiggin at gmail dot com

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-106895-4-nPX7ifMf4P@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).