public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49152] Unhelpful diagnostic for iterator dereference
Date: Sat, 31 Mar 2012 02:16:00 -0000 [thread overview]
Message-ID: <bug-49152-4-rWz7i1kBxY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49152-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49152
--- Comment #24 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-03-31 02:03:02 UTC ---
Personally, I don't believe Gaby is open to other solutions outside the
full-fledged "caret diagnostics" context, thus for the time being at least I'm
personally going to stand to his judgment (as diagnostics maintainer).
next prev parent reply other threads:[~2012-03-31 2:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 21:43 [Bug c++/49152] New: " redi at gcc dot gnu.org
2011-09-21 13:56 ` [Bug c++/49152] " giecrilj at stegny dot 2a.pl
2011-09-21 21:03 ` giecrilj at stegny dot 2a.pl
2011-09-21 21:51 ` redi at gcc dot gnu.org
2011-09-21 23:31 ` manu at gcc dot gnu.org
2011-09-21 23:31 ` redi at gcc dot gnu.org
2011-09-21 23:57 ` redi at gcc dot gnu.org
2011-09-22 0:16 ` manu at gcc dot gnu.org
2011-09-28 0:11 ` giecrilj at stegny dot 2a.pl
2012-03-21 13:25 ` manu at gcc dot gnu.org
2012-03-21 13:30 ` manu at gcc dot gnu.org
2012-03-22 1:53 ` paolo.carlini at oracle dot com
2012-03-22 10:41 ` paolo.carlini at oracle dot com
2012-03-22 11:08 ` redi at gcc dot gnu.org
2012-03-22 11:22 ` redi at gcc dot gnu.org
2012-03-22 11:38 ` manu at gcc dot gnu.org
2012-03-22 12:04 ` redi at gcc dot gnu.org
2012-03-22 13:01 ` manu at gcc dot gnu.org
2012-03-22 14:27 ` suckfish at ihug dot co.nz
2012-03-22 14:34 ` redi at gcc dot gnu.org
2012-03-23 8:20 ` suckfish at ihug dot co.nz
2012-03-24 16:59 ` manu at gcc dot gnu.org
2012-03-31 0:30 ` manu at gcc dot gnu.org
2012-03-31 0:57 ` manu at gcc dot gnu.org
2012-03-31 2:16 ` paolo.carlini at oracle dot com [this message]
2012-03-31 8:24 ` paolo.carlini at oracle dot com
2012-04-01 11:24 ` manu at gcc dot gnu.org
2012-04-01 12:56 ` redi at gcc dot gnu.org
2012-04-01 13:24 ` manu at gcc dot gnu.org
2012-04-01 20:29 ` marc.glisse at normalesup dot org
2012-04-02 5:16 ` jason at gcc dot gnu.org
2012-04-02 8:17 ` manu at gcc dot gnu.org
2012-04-02 15:57 ` jason at gcc dot gnu.org
2012-04-02 17:17 ` manu at gcc dot gnu.org
2012-04-02 17:19 ` manu at gcc dot gnu.org
2012-04-02 17:20 ` manu at gcc dot gnu.org
2012-04-02 17:37 ` pinskia at gmail dot com
2012-04-02 22:06 ` jason at gcc dot gnu.org
2012-04-03 3:42 ` pinskia at gcc dot gnu.org
2012-04-04 15:27 ` manu at gcc dot gnu.org
2012-04-16 15:34 ` paolo at gcc dot gnu.org
2012-04-16 15:36 ` paolo.carlini at oracle dot com
2012-04-16 15:48 ` redi at gcc dot gnu.org
2012-04-16 16:27 ` [Bug c++/49152] pretty printer cannot handle iterators and other complex expressions manu at gcc dot gnu.org
2012-04-23 19:55 ` joseph at codesourcery dot com
2012-04-23 20:28 ` manu at gcc dot gnu.org
2013-03-22 14:48 ` jakub at gcc dot gnu.org
2013-05-31 11:03 ` jakub at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2015-06-22 14:26 ` rguenth at gcc dot gnu.org
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=bug-49152-4-rWz7i1kBxY@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).