public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at libertysurf dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/11271] [3.3.1/3.4 regression] [arm-elf] regex.c ICEs for thumb multilib Date: Wed, 30 Jul 2003 17:14:00 -0000 [thread overview] Message-ID: <20030730171422.13551.qmail@sources.redhat.com> (raw) In-Reply-To: <20030620195357.11271.dhazeghi@yahoo.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11271 ------- Additional Comments From ebotcazou at libertysurf dot fr 2003-07-30 17:14 ------- Subject: Re: [3.4 regression] [arm-elf] regex.c ICEs for thumb multilib > + 2003-03-26 Eric Botcazou <ebotcazou@libertysurf.fr> > + > + PR target/7784 > + * reload.c (find_reloads_address): Handle > + (PLUS (PLUS (REG) (REG)) (CONST_INT)) form for > + all base registers. > + > > As far as I can determine, this is because of the extra constraint added > to the test that ensures that the register being reloaded is valid as a > base register. Unfortunately, this fails on thumb, since SP is not a > valid base register for QImode (so a further reload will be needed). > Prior to this patch we seemed to get things right even without the > additional test. Then this is a thinko in the patch: it was really meant to extend the former code, not to add new restrictions to it. This was needed because we get this form of address (base regs that are not fp/sp) on SPARC sometimes. > Eric, was there a particular reason for adding the test of > REG_MODE_OK_FOR_BASE_P? No, I only mimiced the chunk of code immediately above (or so, I don't have the sources at hand for the time being) that had extended another condition the same way (from fp/sp to all base registers) according to the comment. - Eric
next prev parent reply other threads:[~2003-07-30 17:14 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-20 19:53 [Bug bootstrap/11271] New: " dhazeghi at yahoo dot com 2003-06-20 19:56 ` [Bug bootstrap/11271] " dhazeghi at yahoo dot com 2003-06-20 20:01 ` [Bug bootstrap/11271] [3.4 regression] " dhazeghi at yahoo dot com 2003-06-21 18:38 ` [Bug target/11271] " pinskia at physics dot uc dot edu 2003-07-05 20:22 ` dhazeghi at yahoo dot com 2003-07-05 21:53 ` pinskia at physics dot uc dot edu 2003-07-27 18:51 ` dhazeghi at yahoo dot com 2003-07-27 22:52 ` dhazeghi at yahoo dot com 2003-07-27 22:52 ` dhazeghi at yahoo dot com 2003-07-28 16:46 ` rearnsha at arm dot com 2003-07-29 10:35 ` [Bug target/11271] [3.3.1/3.4 " rearnsha at gcc dot gnu dot org 2003-07-29 14:30 ` pinskia at physics dot uc dot edu 2003-07-30 17:14 ` ebotcazou at libertysurf dot fr [this message] 2003-07-30 20:03 ` pinskia at physics dot uc dot edu 2003-08-19 10:28 ` steve at chelsio dot com 2003-10-16 17:08 ` mmitchel at gcc dot gnu dot org 2003-10-24 16:08 ` dhazeghi at yahoo dot com 2003-10-24 16:10 ` dhazeghi at yahoo dot com 2003-10-29 1:27 ` green at redhat dot com 2003-10-31 12:10 ` cvs-commit at gcc dot gnu dot org 2003-11-02 23:00 ` [Bug target/11271] [3.3.1 " pinskia at gcc dot gnu dot org 2003-11-04 23:59 ` dhazeghi at yahoo dot com 2003-12-12 8:21 ` ebotcazou at gcc dot gnu dot org 2003-12-21 20:25 ` cvs-commit at gcc dot gnu dot org 2003-12-21 20:27 ` gdr at gcc dot gnu dot org 2003-12-21 22:16 ` ebotcazou at gcc dot gnu dot org 2003-12-21 22:21 ` gdr at integrable-solutions dot net 2003-12-21 22:49 ` [Bug optimization/11271] " pinskia at gcc dot gnu dot org 2003-12-22 5:30 ` cvs-commit at gcc dot gnu dot org 2003-12-22 6:07 ` ebotcazou at gcc dot gnu dot org 2004-01-14 8:11 ` [Bug optimization/11271] [3.3 " gdr at gcc dot gnu dot org 2004-01-16 4:02 ` dhazeghi at yahoo dot com 2004-01-16 4:17 ` giovannibajo at libero dot it 2004-01-21 4:08 ` gdr at gcc dot gnu dot org 2004-01-23 9:54 ` rearnsha at gcc dot gnu dot org 2004-01-23 9:54 ` rearnsha at gcc dot gnu dot org 2004-01-23 9:55 ` [Bug optimization/11271] [3.4 " rearnsha at gcc dot gnu dot org
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=20030730171422.13551.qmail@sources.redhat.com \ --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: 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).