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 rtl-optimization/107949] PPC: Unnecessary rlwinm after lbzx
Date: Fri, 17 Feb 2023 17:21:05 +0000 [thread overview]
Message-ID: <bug-107949-4-JEnAO0gi5B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107949-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107949
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #4)
> How would GCC know no extension is needed? The asm template is not parsed
> at all, by design. Making h1 an unsigned char might solve it here?
The version with the inline asm isn't what Jens is worried about, that gives
the generated code he wants (ie, no rlwinm). He asking why the fully C version
of the test case adds the unneeded rlwinm.
next prev parent reply other threads:[~2023-02-17 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:13 [Bug target/107949] New: " jens.seifert at de dot ibm.com
2022-12-02 10:23 ` [Bug target/107949] " jens.seifert at de dot ibm.com
2022-12-02 16:07 ` [Bug rtl-optimization/107949] " pinskia at gcc dot gnu.org
2022-12-10 12:09 ` jens.seifert at de dot ibm.com
2023-01-08 17:31 ` segher at gcc dot gnu.org
2023-02-17 17:21 ` bergner at gcc dot gnu.org [this message]
2023-02-17 17:33 ` 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-107949-4-JEnAO0gi5B@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).