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 unable to specify even/odd register pairs in extended inline asm
Date: Mon, 03 Jul 2023 15:45:52 +0000	[thread overview]
Message-ID: <bug-106895-4-7SmpbG3S9h@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

--- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #5)
> Constraints are completely the wrong tool for this.  Just use modes, which
> *are* the right tool?

Well you cannot specify modes in the asm, so I think you're saying we need use
the correct type that maps to a internal to GCC mode that has the even/odd
register behavior, so something like:

  unsigned int foo __attribute__ ((mode (XX)));

...where XXmode is the new integer mode that gives us even/odd register pairs? 
Of course we have to be careful about how this all works wrt -m32 versus -m64.

  parent reply	other threads:[~2023-07-03 15:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 11:25 [Bug c/106895] New: powerpc64 strange extended inline asm behaviour with register pairs npiggin at gmail dot com
2022-09-09 11:35 ` [Bug c/106895] " rguenth at gcc dot gnu.org
2022-09-09 11:56 ` [Bug target/106895] " bergner at gcc dot gnu.org
2022-09-13 15:34 ` 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 [this message]
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-7SmpbG3S9h@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).