Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!vsi1!daver!bungi.com!news
From: jkp@sauna.hut.fi (Jyrki Kuoppala)
Newsgroups: comp.sys.nsc.32k
Subject: Re: Bug in minix library setjmp.s; lots of GNU tools diffs available
Message-ID: <9102081829.AA05883@cs.hut.fi>
Date: 8 Feb 91 18:29:07 GMT
References: <<9102072106.AA01016@manatee.UUCP>>
Sender: news@daver.bungi.com
Organization: Helsinki University of Technology, Finland.
Lines: 14
Approved: news@daver.bungi.com

>Considering that the setjump issue is a problem that we all share,
>perhaps it would be useful for all of us to adopt a common solution.
>That is, we collectively agree to (a) save all registers, or (b) 
>actively go on a bug hunt :-).  Otherwise, this problem will 
>continue to be a source of frustration, wasted time, generate message
>traffic, etc.
>

Umm, actually I save only the registers that are not allowed to be
clobbered by the gcc calling convention - is there a reason to save
them all (other than someone using -fcall-saved-regs or changing the
convention) ?

//Jyrki