From: Xi Ruoyao <xry111@xry111.site>
To: Jeff Law <jlaw@ventanamicro.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA] [V3] new pass for sign/zero extension elimination
Date: Fri, 05 Jan 2024 04:44:21 +0800 [thread overview]
Message-ID: <42b2069818ecfd370a92c8e318171bfffb521eb0.camel@xry111.site> (raw)
In-Reply-To: <49a49758-e209-4022-991a-b5d3866cf248@ventanamicro.com>
I have successfully bootstrapped and regtested the patch on loongarch64-
linux-gnu. The test cases in the patch (intended for RISC-V) also works
on LoongArch per my manual testing.
On Mon, 2024-01-01 at 14:04 -0700, Jeff Law wrote:
> I know we're deep into stage3 and about to transition to stage4. So if
> the consensus is for this to wait, I'll understand....
>
> This it the V3 of the ext-dce patch based on Joern's work from last year.
>
> Changes since V2:
> Handle MINUS
> Minor logic cleanup for SUBREGs in ext_dce_process_sets
> Includes Joern's carry_backpropagate work
> Cleaned up and removed some use handling code for STRICT_LOW_PART
> Moved non-local goto special case out of main use handling, similar to
> how we handle CALL_INSN_FUSAGE
> Use df_simple_dataflow rather than custom dataflow handling
>
> There's more cleanups we could be doing here, but the question is do we
> stop commit what we've got and iterate on the trunk or do we defer until
> gcc-15 in which case we iterate on a branch or something.
>
> This still is enabled at -O1 or above, but that's to get as much testing
> as possible. Assuming the rest is ACK'd for the trunk we'll put it into
> the list of optimizations enabled by -O2.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-01-04 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 21:04 Jeff Law
2024-01-03 12:07 ` Richard Sandiford
2024-01-03 16:54 ` Richard Sandiford
2024-01-07 23:30 ` Jeff Law
2024-01-08 15:45 ` Richard Sandiford
2024-01-16 15:24 ` Jeff Law
2024-01-04 13:36 ` Stefan Schulze Frielinghaus
2024-01-04 20:07 ` Jeff Law
2024-01-04 20:44 ` Xi Ruoyao [this message]
2024-01-05 16:06 ` Jeff Law
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=42b2069818ecfd370a92c8e318171bfffb521eb0.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.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).