public inbox for
help / color / mirror / Atom feed
From: Phil Blundell <>
Subject: Re: target/2309: [ARM] SUBREG in memory reference
Date: Wed, 23 Jan 2002 02:46:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR target/2309; it has been noted by GNATS.

From: Phil Blundell <>
To: Richard Earnshaw <>
Subject: Re: target/2309: [ARM] SUBREG in memory reference
Date: 23 Jan 2002 10:36:30 +0000

 On Wed, 2002-01-23 at 10:26, Richard Earnshaw wrote:
 >  I have the original post as sent out by gnats, but I can't even extract 
 >  the testcase from that.  So I think it must either have been corrupted 
 >  right up front, or have been a bad attachment in the first place.
 >  However, sleuthing shows that the problem may have been fixed:
 That patch doesn't seem to have been applied to the 3.0 branch or the
 trunk.  They both just say:
 			 Note this assumes that the target dependent
 			 files treat REG and SUBREG equally, including
  			 within GO_IF_LEGITIMATE_ADDRESS and in all the
 			 predicates since we never verify that replacing
  			 the original register with a SUBREG results 
 			 in a recognizable insn.  */
 Do you think GO_IF_LEGITIMATE_ADDRESS in arm.h wants the same treatment
 that mips.h got here, ie this kind of thing:
 	   while (GET_CODE (xinsn) == SUBREG)
 	     xinsn = SUBREG_REG (xinsn);

             reply	other threads:[~2002-01-23 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23  2:46 Phil Blundell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17 10:46 Philip Blundell
2003-05-17 10:42 pb
2003-05-17  9:56 Dara Hazeghi
2002-01-23  2:26 Richard Earnshaw
2002-01-22 13:16 Philip Blundell
2002-01-22 12:37 pb

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).