--- Comment #4 from cm1 at mumac dot de 2010-07-15 10:14 ---
Thanks for the quick explanation and sorry for joining the club of "submit
first, read the specs later" folks -- I actually thought I knew them ;)
It makes of course sense to use volatile in the presence of setjmp/longjmp but
--- Comment #3 from pinskia at gmail dot com 2010-07-15 09:19 ---
Subject: Re: Optimizer doesn't see setjmp()
On Jul 15, 2010, at 2:15 AM, "cm1 at mumac dot de" wrote:
>
>
> --- Comment #1 from cm1 at mumac dot de 2010-07-15 09:15 ---
> Sorry, I edited the contents of the
On Jul 15, 2010, at 2:15 AM, "cm1 at mumac dot de" > wrote:
--- Comment #1 from cm1 at mumac dot de 2010-07-15 09:15 ---
Sorry, I edited the contents of the precompiler output to make it
more readable
and messed up the auto variable name. Please use this code:
#include
#includ
--- Comment #2 from rguenth at gcc dot gnu dot org 2010-07-15 09:18 ---
You need to mark auto variables that are life across setjmp/longjmp calls as
volatile.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #1 from cm1 at mumac dot de 2010-07-15 09:15 ---
Sorry, I edited the contents of the precompiler output to make it more readable
and messed up the auto variable name. Please use this code:
#include
#include
#include
#define EXC_TRY 1
#define EXC_CATCH 2
func()
{
con
