From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Andrew Waterman <andrew@sifive.com>
Subject: [PING][PATCH] RISC-V: Avoid redundant sign-extension for SImode SGE, SGEU, SLE, SLEU
Date: Fri, 25 Nov 2022 14:07:41 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.20.2211251403560.19931@tpp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.2208122258210.10833@tpp.orcam.me.uk>
Hi Kito,
On Fri, 12 Aug 2022, Maciej W. Rozycki wrote:
> > LGTM, but with a nit, I don't get set.w but get an andi like below, so
> > maybe we should also scan-assembler-not andi? feel free to commit that
> > directly with that fix
> >
> > ```asm
> > sleu:
> > sgtu a0,a0,a1 # 9 [c=4 l=4] *sgtu_disi
> > xori a0,a0,1 # 10 [c=4 l=4] *xorsi3_internal/1
> > andi a0,a0,1 # 16 [c=4 l=4] anddi3/1
> > ret # 25 [c=0 l=4] simple_return
> > ```
>
> Interesting. I can do that, but can you please share the compilation
> options, given or defaulted (from `--with...' configuration options), this
> happens with?
I have noticed it went nowhere. Can you please check what compilation
options lead to this discrepancy so that we can have the fix included in
GCC 13? I'd like to understand what's going on here.
Maciej
next prev parent reply other threads:[~2022-11-25 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 9:54 [PATCH] " Maciej W. Rozycki
2022-08-11 3:26 ` Kito Cheng
2022-08-12 22:01 ` Maciej W. Rozycki
2022-11-25 14:07 ` Maciej W. Rozycki [this message]
2022-11-28 14:50 ` [PING][PATCH] " Jeff Law
2022-11-28 15:38 ` Maciej W. Rozycki
2022-11-28 16:15 ` Jeff Law
2022-11-28 17:44 ` [PATCH v2] " Maciej W. Rozycki
2022-11-28 18:07 ` Jeff Law
2022-11-28 19:41 ` Maciej W. Rozycki
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=alpine.DEB.2.20.2211251403560.19931@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
/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).