From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19393 invoked by alias); 31 Oct 2005 16:10:32 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 19349 invoked by uid 48); 31 Oct 2005 16:10:28 -0000 Date: Mon, 31 Oct 2005 16:10:00 -0000 Message-ID: <20051031161028.19348.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/19253] [3.4/4.0/4.1 regression] bad error message / ICE for invalid template parameter In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bangerth at dealii dot org" X-SW-Source: 2005-10/txt/msg04149.txt.bz2 List-Id: ------- 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