public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org> To: wilson@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7871: ICE on legal code, global register variables problems Date: Fri, 28 Feb 2003 16:46:00 -0000 [thread overview] Message-ID: <20030228164601.9872.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7871; it has been noted by GNATS. From: Jim Wilson <wilson@tuliptree.org> To: Richard Henderson <rth@redhat.com> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rz@linux-m68k.org, wilson@gcc.gnu.org Subject: Re: c/7871: ICE on legal code, global register variables problems Date: 28 Feb 2003 11:43:48 -0500 On Fri, 2003-02-28 at 00:47, Richard Henderson wrote: > /* Calls may also reference any of the global registers, > so they are made live. */ > for (i = 0; i < FIRST_PSEUDO_REGISTER; i++) > if (global_regs[i]) > mark_used_reg (pbi, regno_reg_rtx[i], cond, insn); We first call mark_set_1 (... CLOBBER...) which kills the register. Then we call mark_used_reg which makes it live again, and adds a REG_DEAD note to the call. This REG_DEAD note is wrong. This confuses combine into deleting the instruction because there is a REG_DEAD note for it and no visible use of it after combination. It doesn't seem right to modify combine to treat REG_DEAD notes for global regs specially. I think we need to avoid adding the REG_DEAD note in the first place. Maybe what we should do here is call mark_set_reg (...SET...) for global regs instead of mark_set_1 (...CLOBBER...). I think this might work. I will try this. I have some other easier patches to deal with, so I will get back to this later. Jim
next reply other threads:[~2003-02-28 16:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-28 16:46 Jim Wilson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-02 14:16 Richard Zidlicky 2003-05-02 12:26 Richard Zidlicky 2003-05-01 6:06 Jim Wilson 2003-04-06 19:46 Jim Wilson 2003-04-02 20:56 Richard Zidlicky 2003-03-10 5:16 Jim Wilson 2003-02-28 5:56 Richard Henderson 2003-02-28 3:26 Jim Wilson 2003-02-28 3:02 wilson 2002-12-14 12:56 Richard Zidlicky 2002-09-09 14:36 Richard Zidlicky
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=20030228164601.9872.qmail@sources.redhat.com \ --to=wilson@tuliptree.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=wilson@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).