public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Terry Guo" <terry.guo@arm.com>
To: "Richard Earnshaw" <Richard.Earnshaw@arm.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: RE: [GCC, ARM] Backport trunk fix to 4.8 branch to properly handle rtx of ARM PLD instruction
Date: Wed, 15 Jan 2014 12:21:00 -0000	[thread overview]
Message-ID: <000101cf11ec$3628c7b0$a27a5710$@arm.com> (raw)
In-Reply-To: <52D67204.50504@arm.com>

> 
> Preferably, particularly since you haven't supplied a testcase.
> 
> R.

Bug is reported at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59826. I
shall update the patch to include the test case.

BR,
Terry


  reply	other threads:[~2014-01-15 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  9:23 Terry Guo
2014-01-15  9:54 ` Richard Earnshaw
2014-01-15 10:45   ` Terry Guo
2014-01-15 11:33     ` Richard Earnshaw
2014-01-15 12:21       ` Terry Guo [this message]
2014-01-15 12:37       ` Terry Guo
2014-01-15 14:30         ` Richard Earnshaw
2014-01-15 16:00           ` Terry Guo
2014-01-15 16:40             ` Richard Earnshaw

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='000101cf11ec$3628c7b0$a27a5710$@arm.com' \
    --to=terry.guo@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@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).