public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19253] [3.4/4.0/4.1 regression] bad error message / ICE for invalid template parameter
Date: Mon, 31 Oct 2005 16:10:00 -0000	[thread overview]
Message-ID: <20051031161028.19348.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19253-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from bangerth at dealii dot org  2005-10-31 16:10 -------
(In reply to comment #8)
> > How do you generate all these snippets?
> 
> By sheer determination. I pick some topic like pointers-to-members or
> destructors for example and try to find some bugs. Over time you get
> a good feeling for GCC's weaknesses (templates for example). Well,
> okay, maybe those code snippets are "obnoxious".

By the way (should have written this a long time ago): My experience with
things like this is that you should probably save all the snippets you create,
even if they didn't crash the compiler in any interesting way (i.e. worked
just fine). If we ever want to have a comprehensive testsuite, then these
are the pieces that you would want in there.

Of course, getting the gcc folks to accept a thousand small programs that
just test small parts of the language is going to be harder than proposing
a single testcase that shows that a particular patch fixed a particular bug,
but I think it would be worth while.

(For example, if we had had testcases that had stresses static template
members in all their aspects, we would have had a dozen or so regression
reports less lately... :-)

W.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19253


  parent reply	other threads:[~2005-10-31 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19253-1771@http.gcc.gnu.org/bugzilla/>
2005-10-31  2:10 ` mmitchel at gcc dot gnu dot org
2005-10-31 16:10 ` bangerth at dealii dot org [this message]
2005-11-02 21:34 ` mmitchel at gcc dot gnu dot org
2005-11-02 21:35 ` mmitchel at gcc dot gnu dot org
2005-11-02 21:50 ` mmitchel at gcc dot gnu dot org
2005-11-15 19:14 ` reichelt at gcc dot gnu dot org
2005-11-15 19:19 ` reichelt at gcc dot gnu dot org
2005-11-21 15:56 ` pinskia at gcc dot gnu dot org
2006-01-27 16:31 ` pinskia at gcc dot gnu dot org
2005-01-04 14:31 [Bug c++/19253] New: [3.4/4.0 " reichelt at gcc dot gnu dot org
2005-05-19 17:48 ` [Bug c++/19253] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-22 21:18 ` pinskia at gcc dot gnu dot org
2005-09-06 15:27 ` reichelt at gcc dot gnu dot org
2005-09-27 16:24 ` mmitchel at gcc dot gnu dot 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=20051031161028.19348.qmail@sourceware.org \
    --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).