This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/53028] add dg-pedantic
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 23 Apr 2012 21:38:00 +0000
- Subject: [Bug testsuite/53028] add dg-pedantic
- Auto-submitted: auto-generated
- References: <bug-53028-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53028
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-04-23 21:38:00 UTC ---
On Wed, 18 Apr 2012, mikestump at comcast dot net wrote:
> I don't see much value in this. The primary idea of the gcc testsuite is as a
> regression suite. For a regression, there is just one bit of code that you're
> testing, with one set of options.
For more than a decade it's been established that the testsuite should
verify that features or fixes added work as intended; it's not just
testing a particular bug fix, but comprehensively covering the area of a
change. If the intended semantics are pedwarn-if-pedantic, that does mean
testing what happens in three cases. If it's a matter of differences
between standard versions, similarly, testing for each version (and see
the discussion referenced in
<http://gcc.gnu.org/ml/gcc-patches/2000-07/msg00262.html> when I started
adding such tests).
I think features such as dg-pedwarn-if-pedantic or similar would be a
useful addition to the testsuite infrastructure.