From: Andrew MacLeod <amacleod@redhat.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: jakub@redhat.com, jeffreyalaw@gmail.com, gcc-patches@gcc.gnu.org,
richard.guenther@gmail.com, aldyh@redhat.com
Subject: Re: Regression with "recomputation and PR 109154"
Date: Fri, 31 Mar 2023 21:11:54 -0400 [thread overview]
Message-ID: <eb3d3b8d-fa50-944e-5822-af23d5c5b517@redhat.com> (raw)
In-Reply-To: <20230331233122.177D32042C@pchp3.se.axis.com>
On 3/31/23 19:31, Hans-Peter Nilsson wrote:
>> Date: Fri, 31 Mar 2023 15:48:22 -0400
>> From: Andrew MacLeod via Gcc-patches <gcc-patches@gcc.gnu.org>
>> Reply-To: Andrew MacLeod <amacleod@redhat.com>
>> commit 55bf4f0d443e5adbacfcdbbebf4b2e0c74d1dcc8
>> Author: Andrew MacLeod <amacleod@redhat.com>
>> Date: Fri Mar 31 15:42:43 2023 -0400
>>
>> Adjust testcases to not produce errors..
>>
>> tree-optimization/109363
>> gcc/testsuite/
>> * g++.dg/warn/Wstringop-overflow-4.C: Always cehck bogus message.
>> * gcc.dg/tree-ssa/pr23109.c: Disable better recomputations.
>
> (Needs to be spelled "PR tree-optimization/109363" for the
> bugzilla-marker hook to react. I'll mark manually though.)
>
>
Oops! thanks :-)
Andrew
prev parent reply other threads:[~2023-04-01 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 17:22 recomputation and PR 109154 Andrew MacLeod
2023-03-30 6:42 ` Richard Biener
2023-03-30 13:41 ` Jakub Jelinek
2023-03-30 15:58 ` Andrew MacLeod
2023-03-30 16:05 ` Jakub Jelinek
2023-03-30 20:39 ` Andrew MacLeod
2023-03-31 6:08 ` Andrew Pinski
2023-03-31 16:12 ` Regression with "recomputation and PR 109154" Hans-Peter Nilsson
2023-03-31 16:20 ` Jeff Law
2023-03-31 17:02 ` Andrew MacLeod
2023-03-31 17:37 ` Jakub Jelinek
2023-03-31 19:48 ` Andrew MacLeod
2023-03-31 19:59 ` Jeff Law
2023-03-31 20:16 ` Andrew MacLeod
2023-03-31 20:20 ` Jeff Law
2023-03-31 23:31 ` Hans-Peter Nilsson
2023-04-01 1:11 ` Andrew MacLeod [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=eb3d3b8d-fa50-944e-5822-af23d5c5b517@redhat.com \
--to=amacleod@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--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).