From: Jakub Jelinek <jakub@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [LRA] Fix wrong-code PR 91109
Date: Fri, 09 Aug 2019 11:01:00 -0000 [thread overview]
Message-ID: <20190809103745.GZ2726@tucnak> (raw)
In-Reply-To: <VI1PR10MB25732E0B089A3ED81428ECCBE4D60@VI1PR10MB2573.EURPRD10.PROD.OUTLOOK.COM>
On Fri, Aug 09, 2019 at 10:31:57AM +0000, Bernd Edlinger wrote:
> I think this wrong code bug would be good to be fixed in 9.2.
>
> Would you like me to go ahead, or should it wait for 9.3 ?
Wait for 9.2.1 reopening, even if we'd roll another RC, I'd be afraid that
for RA changes, especially ones that aren't a severe recent regression like
this, there is not enough time to have it tested enough.
Jakub
next prev parent reply other threads:[~2019-08-09 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 21:09 Bernd Edlinger
2019-08-07 13:51 ` Vladimir Makarov
2019-08-09 10:59 ` Bernd Edlinger
2019-08-09 11:01 ` Jakub Jelinek [this message]
2019-08-15 19:47 ` [PATCH] [LRA] Fix wrong-code PR 91109 take 2 Bernd Edlinger
2019-08-16 12:07 ` Bernd Edlinger
2019-08-16 15:19 ` Vladimir Makarov
2019-08-16 15:36 ` Vladimir Makarov
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=20190809103745.GZ2726@tucnak \
--to=jakub@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@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).