From: Jason Merrill <jason@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Jeff Law <law@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>,
Marek Polacek <polacek@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] c++/67376 Comparison with pointer to past-the-end, of array fails inside constant expression
Date: Tue, 31 May 2016 20:48:00 -0000 [thread overview]
Message-ID: <CADzB+2=Cj815-xJxH__Q6vbgW7KhzePWc=6TDHT=iw_rZTCRbw@mail.gmail.com> (raw)
In-Reply-To: <574DC76B.2040400@gmail.com>
On Tue, May 31, 2016 at 1:18 PM, Martin Sebor <msebor@gmail.com> wrote:
> On 03/31/2016 11:54 AM, Jason Merrill wrote:
>>
>> OK, thanks.
>
> This bug was fixed in 6.1 but it is also a GCC 5 regression and
> the patch hasn't been applied there yet. Should I go ahead and
> backport it to the 5.x branch?
It seems safe enough to me, but since it touches fold-const let's get
a release manager opinion as well. Jakub?
Jason
next prev parent reply other threads:[~2016-05-31 17:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 21:25 Martin Sebor
2016-03-14 22:13 ` Jakub Jelinek
2016-03-16 19:38 ` Jeff Law
2016-03-16 22:53 ` Jakub Jelinek
2016-03-16 19:53 ` Jeff Law
2016-03-17 21:35 ` Martin Sebor
2016-03-18 17:48 ` Jeff Law
2016-03-21 17:55 ` Jason Merrill
2016-03-21 22:13 ` Jeff Law
2016-03-22 19:10 ` Jason Merrill
2016-03-22 20:38 ` Martin Sebor
2016-03-23 20:41 ` Jason Merrill
2016-03-28 23:20 ` Martin Sebor
2016-03-29 19:07 ` Jason Merrill
2016-03-30 5:56 ` Martin Sebor
2016-03-30 16:02 ` Jason Merrill
2016-03-30 16:58 ` Martin Sebor
2016-03-30 20:19 ` Jason Merrill
2016-03-30 23:09 ` Martin Sebor
2016-03-31 8:48 ` Jason Merrill
2016-03-31 19:30 ` Martin Sebor
2016-03-31 20:07 ` Jason Merrill
2016-05-31 20:33 ` Martin Sebor
2016-05-31 20:48 ` Jason Merrill [this message]
2016-03-31 17:53 ` Jeff Law
2016-03-18 19:13 ` Jeff Law
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='CADzB+2=Cj815-xJxH__Q6vbgW7KhzePWc=6TDHT=iw_rZTCRbw@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=msebor@gmail.com \
--cc=polacek@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).