public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at kernel dot crashing dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/12817] Altivec code generation error with setjmp
Date: Thu, 30 Oct 2003 13:44:00 -0000 [thread overview]
Message-ID: <20031030134414.30672.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031028204226.12817.john.whitney@timesys.com>
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?
next prev parent reply other threads:[~2003-10-30 13:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 20:45 [Bug c/12817] New: " john dot whitney at timesys dot com
2003-10-28 20:52 ` [Bug c/12817] " john dot whitney at timesys dot com
2003-10-30 5:04 ` [Bug target/12817] " pinskia at gcc dot gnu dot org
2003-10-30 13:44 ` segher at kernel dot crashing dot org [this message]
2003-11-18 7:28 ` pinskia at gcc dot gnu dot org
2003-11-21 6:29 ` wilson at gcc dot gnu dot org
2003-11-21 9:23 ` segher at kernel dot crashing dot org
2003-11-21 9:49 ` pinskia at gcc dot gnu dot org
2003-11-28 8:40 ` [Bug target/12817] [SYSV] Altivec code generation error with many registers used pinskia at gcc dot gnu dot org
2003-12-19 6:58 ` pinskia at gcc dot gnu dot org
2004-11-26 9:26 ` amodra at bigpond dot net dot au
2004-11-26 9:54 ` amodra at bigpond dot net dot au
2004-11-26 10:53 ` amodra at bigpond dot net dot au
2004-12-01 5:48 ` cvs-commit at gcc dot gnu dot org
2004-12-01 5:54 ` cvs-commit at gcc dot gnu dot org
2004-12-01 6:13 ` cvs-commit at gcc dot gnu dot org
2004-12-01 6:21 ` amodra at bigpond dot net dot au
2004-12-01 12:37 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031030134414.30672.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).