public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Tim Shen <timshen@google.com>, libstdc++ <libstdc++@gcc.gnu.org>,
	       gcc-patches <gcc-patches@gcc.gnu.org>,
	       Richard Biener <richard.guenther@gmail.com>,
	       "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [Patch, libstdc++/64441] Fix out of range match_results submatch access
Date: Tue, 10 Mar 2015 14:25:00 -0000	[thread overview]
Message-ID: <20150310142455.GF1746@tucnak.redhat.com> (raw)
In-Reply-To: <CAH6eHdTZb6Y-3WMYgJM5a0nd+qy_5QPrLREzU4LN8L45yqVAgQ@mail.gmail.com>

On Tue, Mar 10, 2015 at 02:13:49PM +0000, Jonathan Wakely wrote:
> On 9 March 2015 at 10:56, Tim Shen wrote:
> > I guess this patch doesn't break abi compatibility, so if everything
> > is Ok, I'm gonna patch it to 4.9 too.
> 
> It doesn't change the ABI directly, but it does change the layout of
> the match_results' data on the heap. It mean that instantiations of
> e.g. __regex_algo_impl compiled with GCC 4.9.2 will still call
> __res.resize(n+2) when poopulating a match_results whereas code
> compiled with 4.9.3 would expect to be able to find n+3 sub_match
> objects in the match_results object.
> 
> I think it's safer to not change the branch.
> 
> > I'm not sure if this is a "regression fix" though; if it's
> > inappropriate for trunk, then I can simply wait.
> 
> For the reasons given above, I don't think we want to change this
> between 5.1 and 5.2, but also don't want to wait for 6.0 to fix these
> bugs, so I've CC'd the release managers for their OK.
> 
> RMs: this fixes two bugs in std::regex, which was new in 4.9.0 and is
> still stabilising, as shown by this fix. For the reasons given above I
> think we should fix it on trunk now. The patch has my approval, OK to
> commit?

Ok for trunk.

	Jakub

  reply	other threads:[~2015-03-10 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 10:56 Tim Shen
2015-03-10 14:13 ` Jonathan Wakely
2015-03-10 14:25   ` Jakub Jelinek [this message]
2015-03-10 19:24     ` Tim Shen

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=20150310142455.GF1746@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=timshen@google.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).