This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Bug in expand_builtin_setjmp_receiver ?

From: "Jon Beniston" <jon at beniston dot com>
To: 'FrÃdÃric RISS' <frederic dot riss at gmail dot com>
Cc: <froydnj at codesourcery dot com>, <gcc at gcc dot gnu dot org>
Date: Fri, 29 Oct 2010 18:38:39 +0100
Subject: RE: Bug in expand_builtin_setjmp_receiver ?
References: <00ab01cb7506$5ae12830$10a37890$@beniston.com> <1288200955.1788.1.camel@funkybook>

Hi Fred,

> If you have access to a lm32 toolchain, can you test if gcc.c-
> torture/execute/built-in-setjmp.c passes at different optimization levels?

For a SVN snapshot from yesterday, patched so it fixes the problem Nathan mentioned:

FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O2
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O3 -g
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -Os
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O2 -flto
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution,  -O2 -fwhopr

Cheers,
Jon

References:
- Re: Bug in expand_builtin_setjmp_receiver ?
  - From: Jon Beniston
- Re: Bug in expand_builtin_setjmp_receiver ?
  - From: Frédéric RISS

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]