This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [New testcase] Wrong: "warning: `noreturn' function does return"
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: [New testcase] Wrong: "warning: `noreturn' function does return"
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 08 May 2000 23:38:53 -0600
- cc: aj at suse dot de, rth at cygnus dot com, gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <200005090243.WAA24584@caip.rutgers.edu>you write:
> Is there a way to make a gcc.dg test cycle through -O# options? I
> believe the noreturn-1.c test does something similar to the above
> except that it only does it for -O2. Given that recent optimization
> work broke the noreturn stuff badly, but breakage only occurs at
> specific levels, I'd like to be able to cycle these tests like the
> gcc.c-torture tests do and check various opt levels from 0 to 3.
None that I'm aware of.
jeff