From: Richard Sandiford <richard.sandiford@arm.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, jlaw@ventanamicro.com,
rdapp.gcc@gmail.com, rguenther@suse.de, jakub@redhat.com
Subject: Re: [PATCH] Add a late-combine pass [PR106594]
Date: Wed, 10 Jan 2024 13:01:40 +0000 [thread overview]
Message-ID: <mptle8xuytn.fsf@arm.com> (raw)
In-Reply-To: <mptil473cq9.fsf@arm.com> (Richard Sandiford's message of "Fri, 05 Jan 2024 17:35:10 +0000")
Just a note that, following discussion on IRC, I'll pull this for
GCC 14 and resubmit for GCC 15.
There was also pushback on IRC about making the pass opt-in.
Enabling it for x86_64 would mean fixing RPAD to use a representation
that is more robust against recombination, but as you can imagine, it's
kind-of difficult for me to justify spending significant time fixing an
issue in the x86_64 port. Jeff's testing suggested that there are also
latent issues in the older, less maintained ports.
So to get an idea for expectations: would it be a requirement that a
GCC 15 submission is enabled unconditionally and all known issues in
the ports fixed?
Thanks,
Richard
next prev parent reply other threads:[~2024-01-10 13:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 18:49 Richard Sandiford
2023-11-30 14:10 ` Ping: " Richard Sandiford
2023-12-11 15:23 ` Richard Sandiford
2023-12-11 16:18 ` Robin Dapp
2023-12-30 15:35 ` Ping^3: " Richard Sandiford
2024-01-01 3:11 ` YunQiang Su
2024-01-05 10:10 ` YunQiang Su
2023-12-30 18:13 ` Segher Boessenkool
2024-01-02 9:47 ` Richard Sandiford
2024-06-24 19:37 ` Segher Boessenkool
2024-06-25 10:31 ` Richard Biener
2024-06-25 17:22 ` YunQiang Su
2024-01-03 4:20 ` Jeff Law
2024-01-05 17:35 ` Richard Sandiford
2024-01-08 5:03 ` Jeff Law
2024-01-08 11:52 ` Richard Sandiford
2024-01-08 16:14 ` Jeff Law
2024-01-08 16:59 ` Richard Sandiford
2024-01-08 17:10 ` Jeff Law
2024-01-08 19:11 ` Richard Sandiford
2024-01-08 21:42 ` Jeff Law
2024-01-10 13:01 ` Richard Sandiford [this message]
2024-01-10 13:35 ` Richard Biener
2024-01-10 16:27 ` Jeff Law
2024-01-10 16:40 ` Jeff Law
2024-06-21 4:50 ` Hongtao Liu
2024-06-27 16:49 ` nvptx vs. " Thomas Schwinge
2024-06-27 20:27 ` Thomas Schwinge
2024-06-27 21:20 ` Thomas Schwinge
2024-06-27 22:41 ` Thomas Schwinge
2024-06-28 14:01 ` Richard Sandiford
2024-06-28 16:48 ` Richard Sandiford
2024-07-01 11:55 ` Thomas Schwinge
2024-07-01 11:55 ` WIP Move 'pass_fast_rtl_dce' from 'pass_postreload' into 'pass_late_compilation' (was: nvptx vs. [PATCH] Add a late-combine pass [PR106594]) Thomas Schwinge
2024-06-28 6:07 ` nvptx vs. [PATCH] Add a late-combine pass [PR106594] Roger Sayle
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=mptle8xuytn.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.com \
--cc=rdapp.gcc@gmail.com \
--cc=rguenther@suse.de \
/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).