From: Richard Biener <rguenther@suse.de>
To: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"jakub@redhat.com" <jakub@redhat.com>
Subject: Re: Backport PR91838 and PR110838
Date: Mon, 25 Mar 2024 15:16:08 +0100 (CET) [thread overview]
Message-ID: <no809o38-s0s3-r0oo-q0op-p5353s930718@fhfr.qr> (raw)
In-Reply-To: <64498206-6155-4391-a9a0-4adafda9a4c2@arm.com>
On Mon, 25 Mar 2024, Andre Vieira (lists) wrote:
> Hi,
>
> After the backport off PR target/112787 a failure was reported against x86_64,
> this would be fixed by backporting:
> * tree-optimization/91838 - fix FAIL of g++.dg/opt/pr91838.C
> (d1c072a1c3411a6fe29900750b38210af8451eeb)
> * tree-optimization/110838 - less aggressively fold out-of-bound shifts
> (04aa0edcace22a7815cfc57575f1f7b1f166ac10)
>
> Patches apply cleanly, just one minor git context conflict with includes.
>
> Bootstrapped and regression tested on aarch64-unknown-linux-gnu and
> x86_64-pc-linux-gnu for gcc-12 and gcc-13 branches.
>
> OK to backport?
OK.
Thanks,
Richard.
prev parent reply other threads:[~2024-03-25 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:59 Andre Vieira (lists)
2024-03-25 14:16 ` Richard Biener [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:
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=no809o38-s0s3-r0oo-q0op-p5353s930718@fhfr.qr \
--to=rguenther@suse.de \
--cc=andre.simoesdiasvieira@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).