This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-4.6.3 ICE
On 19 March 2012 14:56, Dennis Clarke wrote:
>
> thus : http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02155.html
>
> ? ? ? ? ? ? ? ?=== gcc tests ===
>
>
> Running target unix
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O0 ?(internal compiler error)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O0 ?(test for excess errors)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O1 ?(internal compiler error)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O1 ?(test for excess errors)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O2 ?(internal compiler error)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O2 ?(test for excess errors)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O3 -fomit-frame-pointer
> (internal compiler error)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O3 -fomit-frame-pointer
> (test for excess errors)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O3 -g ?(internal compiler error)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-O3 -g ?(test for excess errors)
> FAIL: gcc.c-torture/compile/limits-exprparen.c ?-Os ?(internal compiler error)
>
>
> I'd like to extend my stack size a bit and re-run the gcc tests only.
> At the very least I'd like to see gcc.c-torture/compile/limits-exprparen.c run
> again. In detail.
The full output of those tests should still be in a .log file
somewhere under the build dir.
> What would the procedure for that be ?
See http://gcc.gnu.org/install/test.html and
http://gcc.gnu.org/wiki/HowToPrepareATestcase for commands to run
specific tests.
I think you should be able to do something like:
make check RUNTESTFLAGS=compile.exp=gcc.c-torture/compile/limits-exprparen.c