Re: gEDA-user: PCB Polygon code (with r-tree speedups) triggers GCC bug...

[Peter Clifton <pcjc2@xxxxxxxxx>]

On Tue, 2009-02-24 at 12:54 -0500, der Mouse wrote:
> 
> This is the correct fix.  Auto objects which get changed between the
> setjmp and the longjmp are indeterminate after the longjmp, unless
> they
> are declared volatile.  In the words of one setjmp(3) manpage I have
> at
> ready hand:

Thanks Der Mouse, I should have checked the semantics for setjmp /
longjmp before assuming it was a bug.

I guess I'll have to look out for any stack variables used in the
routines which use setjmp / longjmp, and make sure they are not going to
cause trouble.

Since PCB works, I'll assume that the likelihood of that case is low.

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)



_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user