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/37878] [4.4 regression] PPC64 ldu command generated with invalid offset
Date: Wed, 22 Oct 2008 11:35:00 -0000 [thread overview]
Message-ID: <20081022113337.5965.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37878-271@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jakub at gcc dot gnu dot org 2008-10-22 11:33 -------
Created an attachment (id=16526)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16526&action=view)
gcc44-pr37878.patch
Just for the record, after discussions on IRC the bug was identified in
word_offset_memref_operand.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #16519|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37878
next prev parent reply other threads:[~2008-10-22 11:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:32 [Bug target/37878] New: " lucier at math dot purdue dot edu
2008-10-21 0:33 ` [Bug target/37878] " lucier at math dot purdue dot edu
2008-10-21 0:34 ` lucier at math dot purdue dot edu
2008-10-21 8:37 ` schwab at suse dot de
2008-10-21 8:40 ` [Bug target/37878] [4.4 regression] " schwab at suse dot de
2008-10-21 9:56 ` jakub at gcc dot gnu dot org
2008-10-21 14:54 ` dje at gcc dot gnu dot org
2008-10-21 15:12 ` jakub at gcc dot gnu dot org
2008-10-21 15:16 ` dje at gcc dot gnu dot org
2008-10-22 3:33 ` mmitchel at gcc dot gnu dot org
2008-10-22 11:35 ` jakub at gcc dot gnu dot org [this message]
2008-10-23 19:22 ` lucier at math dot purdue dot edu
2008-10-23 21:26 ` lucier at math dot purdue dot edu
2008-10-28 22:37 ` dje at gcc dot gnu dot org
2008-10-28 23:15 ` dje at gcc dot gnu dot org
2008-10-29 8:33 ` jakub at gcc dot gnu dot org
2008-10-29 23:33 ` dje at gcc dot gnu dot org
2008-10-30 0:02 ` lucier at math dot purdue dot edu
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=20081022113337.5965.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).