Re: [Gcc4cli-devel] setjmp

[Andrea C. O. <and...@gm...>]

It changes a lot of files because there is a change in the autotools
version you are using.

Originally we used autoconf 2.59 (quite old) you are using 2.63
It probably changes all Makefile.in configure and config.h and aclocal.m4
It's fine.

I think we can move to a new version.
I even use 2.65 now :)

Andrea

On Fri, Feb 19, 2010 at 11:38 AM, Erven Rohou <erv...@in...> wrote:
> Gabriele Svelto a écrit :
>>
>> 2010/2/19 Erven Rohou <erv...@in...>:
>>>
>>> Ciao,
>>>
>>> Many benchmarks (unfortunately) use setjmp and longjmp, which we do not
>>> support.
>>> However, longjmp is often used to handle exceptional situations, mostly
>>> errors.
>>> Here is a proposal: we could define setjmp to return 0, and longjmp to
>>> abort (or
>>> print a message and abort,...) We could compile and run benchmarks that
>>> do not
>>> have errors. Probably we keep a warning in the header file.
>>> What do you think?
>>
>> Sounds like a good idea, I believe most of the stuff will work well
>> under normal conditions.
>>
>>  Gabriele
>>
>
> Here is a patch for libstd. Please let me know if you have any comment.
> As usual I am having problems with automake/autoconf/etc.
> I modified Makefile.am to add the file setjmp.c. autoreconf generated lots
> of stuff that breaks my build. So I patched Makefile.in by hand. It seems
> that some tool also modified config.h.in and configure.
> Anyway, if somebody has an idea, I am willing do it properly.  :-)
>
> --
> Erven.
>