This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/12817] Altivec code generation error with setjmp
- From: "segher at kernel dot crashing dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Oct 2003 13:44:14 -0000
- Subject: [Bug target/12817] Altivec code generation error with setjmp
- References: <20031028204226.12817.john.whitney@timesys.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12817
------- Additional Comments From segher at kernel dot crashing dot org 2003-10-30 13:44 -------
Subject: Re: Altivec code generation error with setjmp
pinskia at gcc dot gnu dot org wrote:
> On powerpc-apple-darwin in 3.3.2 (20030908), I get:
> mfspr r12,256
> stw r12,-224(r1)
> oris r12,r12,0xdfff
> ori r12,r12,65535
> mtspr 256,r12
> which looks right.
It does.
> on the mainline, GCC does not even save the altivec registers at all (why?).
Why should it save _any_ registers (that are not changed before the call
to setjmp()? setjmp() will just save them again?