public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Manolis Tsamis <manolis.tsamis@vrull.eu>
Cc: Hans-Peter Nilsson <hp@bitrange.com>,
	gcc-patches@gcc.gnu.org,
	Richard Biener <richard.guenther@gmail.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>
Subject: Re: [PATCH v2] Implement new RTL optimizations pass: fold-mem-offsets.
Date: Thu, 13 Jul 2023 10:57:37 -0600	[thread overview]
Message-ID: <27abd14a-67e7-82fc-d1f1-d0a438c09aeb@gmail.com> (raw)
In-Reply-To: <CAM3yNXpAR387RKY67Fs2E8Zjfmru8Q80x7+7Cisd5mJyN6Gh0Q@mail.gmail.com>



On 7/13/23 08:20, Manolis Tsamis wrote:
>>
> I have sent a V3 which contains a number of fixes and improvements:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624439.html
> I tested the new version rebased on master and the m68k issue did not reproduce.
> I don't know what exactly fixed it; do we need to know why or is it
> enough that the issue is gone following some general fixes?
> It is highly possible that this also fixes the x264 failure. Please
> let me know if the issue persists with v3 once you're able to test.
Sounds good.  I'll test both m68k and x264 on rv64 with the latest patch.

jeff

  reply	other threads:[~2023-07-13 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 17:28 Manolis Tsamis
2023-06-17 18:31 ` Jeff Law
2023-07-09 21:37 ` Hans-Peter Nilsson
2023-07-09 21:58   ` Hans-Peter Nilsson
2023-07-12  9:12     ` Manolis Tsamis
2023-07-12 14:13       ` Jeff Law
2023-07-13 14:20         ` Manolis Tsamis
2023-07-13 16:57           ` Jeff Law [this message]
2023-07-12  9:08   ` Manolis Tsamis

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=27abd14a-67e7-82fc-d1f1-d0a438c09aeb@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@bitrange.com \
    --cc=manolis.tsamis@vrull.eu \
    --cc=philipp.tomsich@vrull.eu \
    --cc=richard.guenther@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).