public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "npiggin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106895] New: powerpc64 strange extended inline asm behaviour with register pairs Date: Fri, 09 Sep 2022 11:25:09 +0000 [thread overview] Message-ID: <bug-106895-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106895 Bug ID: 106895 Summary: powerpc64 strange extended inline asm behaviour with register pairs Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: npiggin at gmail dot com CC: segher at gcc dot gnu.org Target Milestone: --- Target: powerpc64le-linux-gnu This is Debian 12.2.0-1 build. powerpc64 instructions operating on 128 bits use "even/odd pair" of adjacent GPRs, where the lower numbered register specifies the pair and it must be an even number. This code compiled with -O2: void set128(__int128 val, __int128 *mem) { #if WORKAROUND asm(""); #endif asm("stq %1,%0" : "=m"(*mem) : "r"(val)); } Results in an invalid even/odd pair: stq 3,0(5) blr If compiled with -DWORKAROUND it results in a valid pair: mr 10,3 mr 11,4 stq 10,0(5) blr
next reply other threads:[~2022-09-09 11:25 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-09 11:25 npiggin at gmail dot com [this message] 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 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@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).