From: Jakub Jelinek <jakub@redhat.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, chenglulu <chenglulu@loongson.cn>,
i@xen0n.name, xuchenghua@loongson.cn, c@jia.je
Subject: Re: [PATCH] middle-end: Call negate_rtx instead of simplify_gen_unary expanding rotate shift [PR113033]
Date: Mon, 18 Dec 2023 18:45:30 +0100 [thread overview]
Message-ID: <ZYCFOlTpYdXcJgei@tucnak> (raw)
In-Reply-To: <d844abec473247365cf7f5d079984d74b6d20120.camel@xry111.site>
On Tue, Dec 19, 2023 at 12:48:46AM +0800, Xi Ruoyao wrote:
> > > gcc/ChangeLog:
> > >
> > > PR middle-end/113033
> > > * expmed.cc (expand_shift_1): When expanding rotate shift, call
> > > negate_rtx instead of simplify_gen_unary (NEG, ...).
>
> > The key difference being that using negate_rtx will go through the
> > expander which knows how to synthesize negation whereas
> > simplify_gen_unary will just generate a (neg ...) and assume it matches
> > something in the backend, right?
>
> For PR113033 the key difference (to me) is negate_rtx emits an insn to
> set a new pseudo reg to -x. So the result will be
>
> (set (reg:SI 81) (neg:SI (reg:SI 80)))
>
> then
>
> (and (reg:SI 81) (const_int 31))
>
> instead of a consolidated
>
> (and:SI (neg:SI (reg:SI IN)) (const_int 63))
>
> AFAIK no backends have an instruction doing "negate an operand then and
> bitwisely".
Can you explain why it doesn't work as is though?
I mean, expand_shift_1 with that (and (neg (reg ...)) (const_int ...))
should try to legitimize the operand (e.g. in maybe_legitimize_operand
-> force_operand and force_operand should be able to deal with that,
AND is binary op, so it recurses on the 2 operands and NEG is UNARY_P,
so the recursion should deal with that if it is not general_operand.
Jakub
next prev parent reply other threads:[~2023-12-18 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 13:42 Xi Ruoyao
2023-12-18 15:39 ` Jeff Law
2023-12-18 16:48 ` Xi Ruoyao
2023-12-18 17:45 ` Jakub Jelinek [this message]
2023-12-18 20:01 ` Xi Ruoyao
2023-12-18 20:15 ` Jakub Jelinek
2023-12-18 20:18 ` Xi Ruoyao
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=ZYCFOlTpYdXcJgei@tucnak \
--to=jakub@redhat.com \
--cc=c@jia.je \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=jeffreyalaw@gmail.com \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).