Hi Mike,

Is it ok to document this feature in README.gcc? Is it ok to back port this
feature to 4.7 branch? Thanks.

BR,
Terry

> -----Original Message-----
> From: Terry Guo [mailto:terry....@arm.com]
> Sent: Thursday, August 30, 2012 10:45 AM
> To: 'Mike Stump'
> Cc: gcc-patches@gcc.gnu.org; Richard Guenther
> Subject: RE: [Patch, test] Enable to prune warnings for tests defined
> in one exp file
> 
> > -----Original Message-----
> > From: Mike Stump [mailto:mikest...@comcast.net]
> > Sent: Tuesday, August 28, 2012 1:21 AM
> > To: Terry Guo
> > Cc: gcc-patches@gcc.gnu.org; Richard Guenther
> > Subject: Re: [Patch, test] Enable to prune warnings for tests defined
> > in one exp file
> >
> > On Aug 27, 2012, at 1:14 AM, Terry Guo wrote:
> > > This patch intends to provide a chance to prune common warning
> > messages for
> > > tests defined in an exp file.
> >
> > > Is it OK to trunk?
> >
> > Ok.
> >
> > If you can find where to document this...  :-)  That'd be nice.
> >
> 
> I checked the texi files in gcc/doc folder, but can't find a suitable
> place. So I resort to README.gcc in gcc/testsuite which is claimed to
> list notes for those writing testcases and those writing expect scripts.
> Following is the patch. Is it OK?
> 
> BR,
> Terry
> 
> 2012-08-30  Terry Guo  <terry....@arm.com>
> 
>         * README.gcc: Document new variable dg_runtest_extra_prunes.
> 
> Index: gcc/testsuite/README.gcc
> ===================================================================
> --- gcc/testsuite/README.gcc  (revision 190795)
> +++ gcc/testsuite/README.gcc  (working copy)
> @@ -79,6 +79,11 @@
> 
>  If a test does not fit into the torture framework, use the dg
> framework.
> 
> +If some tests in an exp file need to skip same warning messages, just
> define
> +variable dg_runtest_extra_prunes in this exp file and let it contain
> this warning
> +message pattern.  This can avoid duplicating dg-prune in these cases.
> +Always remember to clear this variable when leave this exp file.
> +
> 
> 
>  Copyright (C) 1997, 1998, 2004 Free Software Foundation, Inc.


Reply via email to