public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Blundell <pb@nexus.co.uk> To: pb@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/2309: [ARM] SUBREG in memory reference Date: Wed, 23 Jan 2002 02:46:00 -0000 [thread overview] Message-ID: <20020123104608.23352.qmail@sources.redhat.com> (raw) The following reply was made to PR target/2309; it has been noted by GNATS. From: Phil Blundell <pb@nexus.co.uk> To: Richard Earnshaw <rearnsha@arm.com> Cc: gcc-gnats@gcc.gnu.org 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: > > http://gcc.gnu.org/ml/gcc-patches/2001-04/msg00131.html 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. */ > http://gcc.gnu.org/ml/gcc-patches/1999-06/msg00419.html 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); p.
next 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: 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=20020123104608.23352.qmail@sources.redhat.com \ --to=pb@nexus.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=pb@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: linkBe 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).