public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/23392] [4.1 Regression] foward-1.m fails with -funroll-loops -O3 -fgnu-runtime Date: Wed, 16 Nov 2005 01:04:00 -0000 [thread overview] Message-ID: <20051116010407.13578.qmail@sourceware.org> (raw) In-Reply-To: <bug-23392-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from amodra at gcc dot gnu dot org 2005-11-16 01:04 ------- Subject: Bug 23392 Author: amodra Date: Wed Nov 16 01:03:58 2005 New Revision: 107060 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107060 Log: PR rtl-optimization/23392 * regrename.c (enum scan_actions) Add mark_access. (scan_actions_name): Ditto. (scan_rtx_reg): Handle mark_access. (scan_rtx_address): Do nothing for mark_access. (build_def_use): Mark source registers in REG_FRAME_RELATED_EXPR and regs in REG_INC notes before closing chains for dead regs. Mark destination regs in REG_FRAME_RELATED_EXPR notes after opening chains for new writes. Modified: branches/gcc-4_0-branch/gcc/ChangeLog branches/gcc-4_0-branch/gcc/regrename.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23392
next prev parent reply other threads:[~2005-11-16 1:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23392-6528@http.gcc.gnu.org/bugzilla/> 2005-10-24 18:05 ` pinskia at gcc dot gnu dot org 2005-10-24 18:55 ` dalej at gcc dot gnu dot org 2005-10-24 21:41 ` dalej at gcc dot gnu dot org 2005-10-27 0:08 ` pinskia at gcc dot gnu dot org 2005-10-31 5:03 ` mmitchel at gcc dot gnu dot org 2005-11-05 10:31 ` steven at gcc dot gnu dot org 2005-11-05 14:14 ` pinskia at gcc dot gnu dot org 2005-11-08 5:23 ` amodra at bigpond dot net dot au 2005-11-08 5:24 ` amodra at bigpond dot net dot au 2005-11-16 0:22 ` amodra at gcc dot gnu dot org 2005-11-16 1:04 ` amodra at gcc dot gnu dot org [this message] 2005-11-16 1:05 ` amodra at bigpond dot net dot au
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=20051116010407.13578.qmail@sourceware.org \ --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).