public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com> To: rearnsha@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5712: [ARM] bad ADR generated Date: Fri, 15 Mar 2002 08:46:00 -0000 [thread overview] Message-ID: <20020315164601.8786.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5712; it has been noted by GNATS. From: Richard Earnshaw <rearnsha@arm.com> To: pb@nexus.co.uk Cc: gcc-gnats@gcc.gnu.org, Richard.Earnshaw@arm.com, gcc-patches@gcc.gnu.org Subject: Re: target/5712: [ARM] bad ADR generated Date: Fri, 15 Mar 2002 16:38:19 +0000 This is a multipart MIME message. --==_Exmh_-11356120700 Content-Type: text/plain; charset=us-ascii It turns out that this is due to an adr insn which was suddenly being used when it had no right to be (because we can't determine how far away the target will be). Fortunately, that pattern is now dead; it was originally added for an earlier constant pool handling rewrite, but subsequent changes have made it redundant. I've deleted the expand and its matcher. R. 2002-03-15 Richard Earnshaw <rearnsha@arm.com> PR target/5712 * arm.md (movaddr, movaddr_insn): Delete. --==_Exmh_-11356120700 Content-Type: text/x-patch ; name="gcc-movaddr.patch"; charset=us-ascii Content-Description: gcc-movaddr.patch Content-Disposition: attachment; filename="gcc-movaddr.patch" Index: config/arm/arm.md =================================================================== RCS file: /cvs/gcc/gcc/gcc/config/arm/arm.md,v retrieving revision 1.90 diff -p -r1.90 arm.md *** arm.md 2002/03/14 22:34:00 1.90 --- arm.md 2002/03/15 16:29:10 *************** *** 4132,4158 **** }" ) - (define_expand "movaddr" - [(set (match_operand:SI 0 "s_register_operand" "") - (match_operand:DI 1 "address_operand" ""))] - "TARGET_ARM" - "" - ) - - (define_insn "*movaddr_insn" - [(set (match_operand:SI 0 "s_register_operand" "=r") - (match_operand:DI 1 "address_operand" "p"))] - "TARGET_ARM - && reload_completed - && (GET_CODE (operands[1]) == LABEL_REF - || (GET_CODE (operands[1]) == CONST - && GET_CODE (XEXP (operands[1], 0)) == PLUS - && GET_CODE (XEXP (XEXP (operands[1], 0), 0)) == LABEL_REF - && GET_CODE (XEXP (XEXP (operands[1], 0), 1)) == CONST_INT))" - "adr%?\\t%0, %a1" - [(set_attr "predicable" "yes")] - ) - ;; When generating pic, we need to load the symbol offset into a register. ;; So that the optimizer does not confuse this with a normal symbol load ;; we use an unspec. The offset will be loaded from a constant pool entry, --- 4132,4137 ---- --==_Exmh_-11356120700--
next reply other threads:[~2002-03-15 16:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-15 8:46 Richard Earnshaw [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-15 8:48 rearnsha 2002-03-15 3:03 rearnsha 2002-02-17 3:26 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=20020315164601.8786.qmail@sources.redhat.com \ --to=rearnsha@arm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=rearnsha@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).