public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35907] [4.3/4.4 Regression] 64-bit power6 glibc miscompilation
Date: Fri, 11 Apr 2008 17:21:00 -0000 [thread overview]
Message-ID: <20080411172043.8510.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35907-87@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from bergner at gcc dot gnu dot org 2008-04-11 17:20 -------
Created an attachment (id=15467)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15467&action=view)
Restore altivec regs after frame pointer setup
I agree with Andrew, it looks like Eric's patch moved the restoring of the
altivec registers to before the frame pointer code. The attached (non
bootstrapped or regtested) fixes the problem for me. Does this look ok to
everyone?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35907
next prev parent reply other threads:[~2008-04-11 17:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 13:57 [Bug target/35907] New: " jakub at gcc dot gnu dot org
2008-04-11 14:02 ` [Bug target/35907] " jakub at gcc dot gnu dot org
2008-04-11 14:26 ` jakub at gcc dot gnu dot org
2008-04-11 14:32 ` jakub at gcc dot gnu dot org
2008-04-11 16:27 ` pinskia at gcc dot gnu dot org
2008-04-11 17:21 ` bergner at gcc dot gnu dot org [this message]
2008-04-11 17:34 ` bergner at gcc dot gnu dot org
2008-04-11 18:38 ` jakub at gcc dot gnu dot org
2008-04-11 19:08 ` pinskia at gcc dot gnu dot org
2008-04-11 19:09 ` bergner at gcc dot gnu dot org
2008-04-11 19:20 ` jakub at gcc dot gnu dot org
2008-04-11 22:05 ` bergner at gcc dot gnu dot org
2008-04-14 7:19 ` amodra at bigpond dot net dot au
2008-04-14 7:31 ` jakub at gcc dot gnu dot org
2008-04-14 10:26 ` amodra at bigpond dot net dot au
2008-04-15 9:26 ` jakub at gcc dot gnu dot org
2008-04-15 12:35 ` jakub at gcc dot gnu dot org
2008-04-15 14:37 ` bergner at gcc dot gnu dot org
2008-04-15 21:16 ` bergner at gcc dot gnu dot org
2008-04-16 0:42 ` amodra at bigpond dot net dot au
2008-04-16 0:44 ` pinskia at gcc dot gnu dot org
2008-04-17 7:21 ` jakub at gcc dot gnu dot org
2008-04-17 12:29 ` amodra at gcc dot gnu dot org
2008-04-17 12:29 ` amodra at gcc dot gnu dot org
2008-04-17 12:30 ` amodra at bigpond dot net dot au
2008-04-18 19:13 ` jakub at gcc dot gnu dot org
2008-04-18 19:15 ` jakub 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=20080411172043.8510.qmail@sourceware.org \
--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).