This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Glitch in gcc.dg/20000623-1.c
On Mon, Jun 26, 2000 at 11:37:09AM -0700, Geoff Keating wrote:
> > From: Zack Weinberg <zack@wolery.cumb.org>
> > Date: Sun, 25 Jun 2000 20:52:48 -0700
> > Content-Disposition: inline
> > User-Agent: Mutt/1.2i
> >
> > gcc.dg tests need to prototype exit and abort if they use them.
>
> Oops! Yes, this is fine. I think you can commit it as an obvious fix
> if you haven't already.
I did already check it in.
> > Note this particular test might be better off in gcc.c-torture with an
> > .x file.
>
> The .x file lets you change the options? It's a gcc.dg test so that
> it can always have -fno-strict-aliasing.
Yes. In c-torture/execute, you can get the same effect as the
dg-options line by creating 20000623-1.x with the contents
set additional_flags="-fno-strict-aliasing"
return 0
The advantage of doing it this way is you still get c-torture's cycle
through optimization levels.
In c-torture/compile, the same trick works but you have to say
`set options="..."' instead of additional_flags.
zw