public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com> 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:26:00 -0000 [thread overview] Message-ID: <20020123102602.2313.qmail@sources.redhat.com> (raw) The following reply was made to PR target/2309; it has been noted by GNATS. From: Richard Earnshaw <rearnsha@arm.com> To: Philip Blundell <philb@gnu.org> Cc: bernds@redhat.com, richard.earnshaw@arm.com, gcc-gnats@gcc.gnu.org Subject: Re: target/2309: [ARM] SUBREG in memory reference Date: Wed, 23 Jan 2002 10:23:17 +0000 > Does anybody know what the status of this is now? > > I don't seem to have a copy of the original testcase any more, and the > one in GNATS appears to be corrupt, so I can't easily test whether the > bug still happens. (Even if I did have that testcase, I guess there's a > good chance that it would no longer generate the problematic RTL in any > case > > From a quick look at GO_IF_LEGITIMATE_ADDRESS in arm.h from the 3.0 > branch, it seems to me that it's still not prepared to handle SUBREGs in > memory expressions. > > 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 http://gcc.gnu.org/ml/gcc-patches/1999-06/msg00419.html R.
next reply other threads:[~2002-01-23 10:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-23 2:26 Richard Earnshaw [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:46 Phil Blundell 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=20020123102602.2313.qmail@sources.redhat.com \ --to=rearnsha@arm.com \ --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).