public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36090] [4.3/4.4 Regression] ppc64 cacoshl miscompilation
Date: Sun, 04 May 2008 19:48:00 -0000 [thread overview]
Message-ID: <20080504194723.21953.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36090-87@http.gcc.gnu.org/bugzilla/>
------- Comment #26 from jakub at gcc dot gnu dot org 2008-05-04 19:47 -------
Created an attachment (id=15576)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15576&action=view)
gcc44-pr36090.patch
Patch I've bootstrapped on 4.3 branch on {i386,x86_64,ppc,ppc64}-linux, no
regressions.
Note that while this fixes this regression, IMNSHO rs6000_legitimate_address
check needs to be tightened up anyway, to match what the output routine
actually accepts (with current print_operand_address code the first MINUS when
going through XEXP (x, 0) must be symbol - .LCTOC*).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36090
next prev parent reply other threads:[~2008-05-04 19:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:16 [Bug target/36090] New: " jakub at gcc dot gnu dot org
2008-04-30 20:16 ` [Bug target/36090] " jakub at gcc dot gnu dot org
2008-04-30 20:26 ` jakub at gcc dot gnu dot org
2008-04-30 20:39 ` jakub at gcc dot gnu dot org
2008-04-30 21:18 ` dje at gcc dot gnu dot org
2008-05-01 2:33 ` dje at gcc dot gnu dot org
2008-05-01 2:41 ` dje at gcc dot gnu dot org
2008-05-01 7:14 ` jakub at gcc dot gnu dot org
2008-05-01 15:08 ` dje at gcc dot gnu dot org
2008-05-01 15:47 ` dje at gcc dot gnu dot org
2008-05-01 17:16 ` jakub at gcc dot gnu dot org
2008-05-01 17:34 ` dje at gcc dot gnu dot org
2008-05-02 9:35 ` jakub at gcc dot gnu dot org
2008-05-02 9:47 ` jakub at gcc dot gnu dot org
2008-05-02 12:42 ` dje at gcc dot gnu dot org
2008-05-02 15:11 ` dje at gcc dot gnu dot org
2008-05-02 15:44 ` dje at gcc dot gnu dot org
2008-05-02 15:46 ` dje at gcc dot gnu dot org
2008-05-02 16:30 ` bonzini at gnu dot org
2008-05-02 17:37 ` dje at gcc dot gnu dot org
2008-05-02 21:08 ` bonzini at gnu dot org
2008-05-02 21:24 ` dje at gcc dot gnu dot org
2008-05-03 7:13 ` bonzini at gnu dot org
2008-05-03 13:22 ` dje at gcc dot gnu dot org
2008-05-03 13:26 ` bonzini at gnu dot org
2008-05-03 14:21 ` dje at gcc dot gnu dot org
2008-05-03 15:48 ` bonzini at gnu dot org
2008-05-04 19:48 ` jakub at gcc dot gnu dot org [this message]
2008-05-04 20:09 ` dje at gcc dot gnu dot org
2008-05-08 16:37 ` dje at gcc dot gnu dot org
2008-05-08 16:41 ` dje at gcc dot gnu dot org
2008-05-09 5:37 ` cnstar9988 at gmail dot com
2008-05-09 14:19 ` jakub at gcc dot gnu dot org
2008-05-09 14:33 ` jakub at gcc dot gnu dot org
2008-05-09 15:52 ` bonzini at gnu dot org
2008-05-09 17:15 ` dje at gcc dot gnu dot org
2008-05-12 15:51 ` bonzini at gnu dot org
2008-05-12 16:33 ` dje at gcc dot gnu dot org
2008-05-12 16:48 ` bonzini at gnu dot org
2008-05-12 16:52 ` dje at gcc dot gnu dot org
2008-05-12 16:55 ` bonzini at gnu dot org
2008-05-16 19:45 ` rguenth at gcc dot gnu dot org
2008-05-18 18:32 ` jakub at gcc dot gnu dot org
2008-05-18 20:20 ` jakub at gcc dot gnu dot org
2008-05-18 20:21 ` jakub at gcc dot gnu dot org
2008-05-18 20:25 ` 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=20080504194723.21953.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).