public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org To: 168086@bugs.debian.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, james@nocrew.org, nobody@gcc.gnu.org Subject: Re: target/9090: arm ICE with >= -O2; regression from 2.95 Date: Sat, 11 Jan 2003 17:04:00 -0000 [thread overview] Message-ID: <20030111170458.4472.qmail@sources.redhat.com> (raw) Synopsis: arm ICE with >= -O2; regression from 2.95 State-Changed-From-To: open->analyzed State-Changed-By: rearnsha State-Changed-When: Sat Jan 11 09:04:58 2003 State-Changed-Why: The cause of PR 9090 comes from the fact that when we have (insn 127 126 128 1 0x40c653c8 (set (reg:SI 1 r1) (reg:SI 59)) 161 {*arm_movsi_insn} (nil) (expr_list:REG_EQUAL (addressof:SI (reg/v:DI 56) 55 0x40aa48c0) (nil))) purge_addressof_1, when applied to the notes fails to purge the address, instead giving just (insn 127 126 128 1 0x40c653c8 (set (reg:SI 1 r1) (reg:SI 59)) 161 {*arm_movsi_insn} (nil) (expr_list:REG_EQUAL (addressof:SI (mem/s:DI (plus:SI (reg/f:SI 25 sfp) (const_int -16 [0xfffffff0])) [14 S8 A32]) 55 0x40aa48c0) That is, it's pushed the referenced register onto the stack, but then failed to simplify the resulting addressof expression. However, the patch seems so simple that I'm concerned that I've missed somthing obvious. Would someone care to comment? No regressions shown by an arm-elf cross build. <date> Richard Earnshaw <rearnsha@arm.com> * function.c (purge_addressof_1): After pushing an addressed register onto the stack, simplify the result. 2. addressof.patch (text/x-patch) This is a text/x-patch It might be displayable with metamail. (Invoke menu with right button.) Index: function.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/function.c,v retrieving revision 1.392 diff -p -r1.392 function.c *** function.c 10 Jan 2003 02:22:01 -0000 1.392 --- function.c 11 Jan 2003 16:57:16 -0000 *************** purge_addressof_1 (loc, insn, force, sto *** 3007,3016 **** rtx sub, insns; if (GET_CODE (XEXP (x, 0)) != MEM) ! { ! put_addressof_into_stack (x, ht); ! return true; ! } /* We must create a copy of the rtx because it was created by overwriting a REG rtx which is always shared. */ --- 3007,3013 ---- rtx sub, insns; if (GET_CODE (XEXP (x, 0)) != MEM) ! put_addressof_into_stack (x, ht); /* We must create a copy of the rtx because it was created by overwriting a REG rtx which is always shared. */ http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9090
next reply other threads:[~2003-01-11 17:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-11 17:04 rearnsha [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-29 7:36 Matthias Klose
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=20030111170458.4472.qmail@sources.redhat.com \ --to=rearnsha@gcc.gnu.org \ --cc=168086@bugs.debian.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=james@nocrew.org \ --cc=nobody@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).