public inbox for
 help / color / mirror / Atom feed
From: Jeff Law <>
To: Robin Dapp <>, "H.J. Lu" <>,
	GCC Patches <>
Subject: Re: [RFC] postreload cse'ing vector constants
Date: Sun, 20 Nov 2022 09:40:14 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/3/22 06:38, Robin Dapp wrote:
> Should we go ahead with this, i.e. push the change and wait for fallout?
>   I guess we're still early enough in the cycle for that.  There are no
> regressions anymore on s390, Power9, x86 and aarch64 (at least on the
> farm machines I checked).

That would be my recommendation (go forward asap so that there's more 
time to find any fallout).


      reply	other threads:[~2022-11-20 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 14:40 Robin Dapp
2022-09-07 15:06 ` Jeff Law
2022-09-07 15:33   ` Robin Dapp
2022-09-07 15:49     ` Jeff Law
2022-09-08 13:04       ` Robin Dapp
2022-09-27 17:40         ` Robin Dapp
2022-09-27 19:39           ` H.J. Lu
2022-09-28 16:48             ` Robin Dapp
2022-11-03 12:38               ` Robin Dapp
2022-11-20 16:40                 ` Jeff Law [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).