public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: libstdc++@gcc.gnu.org, gcc@gcc.gnu.org
Subject: RFC: c++ diagnostics
Date: Mon, 05 Apr 2010 15:20:00 -0000	[thread overview]
Message-ID: <20100405082033.7a9bcf81@redhat.com> (raw)


Hello all! 

I've put up a short diagnostics comparison between gcc, icc, and
clang. It is my plan to update this with major revisions to individual
compilers. 

Included are most of the outstanding bugzilla requests with the
"diagnostic" keyword. However, I am looking for help! Please send me
code samples that frustrate, obfuscate, and annoy. 

In particular, I am looking for template instantiation issues such as
c++/41884, but hopefully something in a deliciously small snippet. No
doubt other C++ hackers have particular annoyances.

I'm also looking for guidance on how to rank the priority of these
issues. Is there some way to tell what the biggest annoyance is?

http://people.redhat.com/bkoz/diagnostics/diagnostics.html

best,
benjamin

             reply	other threads:[~2010-04-05 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 15:20 Benjamin Kosnik [this message]
2010-04-05 17:24 ` Chris Lattner
2010-04-05 19:51   ` Benjamin Kosnik
2010-04-05 19:54     ` Chris Lattner
2010-04-05 18:59 ` Manuel López-Ibáñez
2010-04-05 19:44   ` Benjamin Kosnik
2010-04-06 16:00 ` Chris Lattner
2010-04-06 16:20   ` Joe Buck
2010-04-06 16:29   ` Manuel López-Ibáñez
2010-04-06 16:45     ` Chris Lattner
2010-04-06 19:03       ` Joe Buck
2010-04-06 21:02         ` Laurent GUERBY
2010-04-07  6:46           ` Robert Dewar
2010-04-14  6:24 ` Manuel López-Ibáñez
2010-04-14 13:18 ` Manuel López-Ibáñez

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=20100405082033.7a9bcf81@redhat.com \
    --to=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@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).