From: "Daniel Krügler" <daniel.kruegler@gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [patch] Make vector::at() assertion message more useful (try #2)
Date: Thu, 05 Sep 2013 04:55:00 -0000 [thread overview]
Message-ID: <CAGNvRgD6mK=-n7QhK=-NtfXZHOpCniXKc-riWUNfqZeVa8xufQ@mail.gmail.com> (raw)
In-Reply-To: <CALoOobMf3u8R_DVW5b2eRy05fBpB5unhriLMYdUEkT_E3DwtaA@mail.gmail.com>
2013/9/5 Paul Pluzhnikov <ppluzhnikov@google.com>:
> On Wed, Sep 4, 2013 at 2:10 PM, Daniel Krügler
> <daniel.kruegler@gmail.com> wrote:
>
>> I expect that this kind of index violation is a rather often occurring
>> pattern and should be isolated. IMO the _M_range
>> _check now pessimisms the normal, non-violating case.
>
> Did you mean "pessimises code size", or something else?
Yes.
- Daniel
next prev parent reply other threads:[~2013-09-05 4:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 20:53 Paul Pluzhnikov
2013-09-04 21:10 ` Daniel Krügler
2013-09-04 23:17 ` Paul Pluzhnikov
2013-09-05 4:55 ` Daniel Krügler [this message]
2013-09-13 5:19 ` Paul Pluzhnikov
2013-09-13 10:52 ` Paolo Carlini
2013-09-18 20:30 ` Paul Pluzhnikov
2013-09-18 23:24 ` Paolo Carlini
2013-09-22 10:19 ` Paul Pluzhnikov
2013-09-23 11:09 ` Andreas Schwab
2013-09-23 11:45 ` Paolo Carlini
2013-09-23 12:54 ` Richard Biener
2013-09-23 12:59 ` Andreas Schwab
2013-09-23 13:40 ` Paolo Carlini
2013-09-23 13:42 ` Andreas Schwab
2013-09-23 14:12 ` Paolo Carlini
2013-09-23 14:12 ` Marc Glisse
2013-09-23 14:12 ` Jakub Jelinek
2015-04-06 11:37 ` [wwwdocs] Testing C++ changes (was: [patch] Make vector::at() assertion message more useful) Gerald Pfeifer
2015-04-06 14:06 ` [wwwdocs] Testing C++ changes Jason Merrill
2013-09-23 15:18 ` [patch] Make vector::at() assertion message more useful (try #2) Paul Pluzhnikov
2013-09-23 15:26 ` Paolo Carlini
2013-09-23 16:38 ` Paul Pluzhnikov
2013-09-23 17:00 ` Paolo Carlini
2013-09-23 17:01 ` Paul Pluzhnikov
2013-09-23 16:21 ` Paul Pluzhnikov
2013-09-04 23:26 ` Paolo Carlini
2013-09-04 23:36 ` Paul Pluzhnikov
2013-09-04 23:44 ` Paolo Carlini
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='CAGNvRgD6mK=-n7QhK=-NtfXZHOpCniXKc-riWUNfqZeVa8xufQ@mail.gmail.com' \
--to=daniel.kruegler@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ppluzhnikov@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).