public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/29877] out of SSA (TER) extends variable life of variable beyond original declared Date: Sat, 18 Nov 2006 18:20:00 -0000 [thread overview] Message-ID: <20061118182006.7907.qmail@sourceware.org> (raw) In-Reply-To: <bug-29877-13580@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from amacleod at redhat dot com 2006-11-18 18:20 ------- Yes, I think that is sufficient. I beleive all register variables have to be loaded into an SSA_NAME like this before they can be used, and they all have to have a virtual operand. So it should be good. You beat me to it :-) Andrew -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29877
next prev parent reply other threads:[~2006-11-18 18:20 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-17 17:58 [Bug tree-optimization/29877] New: Tree optimization " diego dot dompe at ridgerun dot com 2006-11-17 18:31 ` [Bug tree-optimization/29877] out of SSA (TER) " pinskia at gcc dot gnu dot org 2006-11-17 19:28 ` amacleod at redhat dot com 2006-11-18 4:58 ` shinwell at gcc dot gnu dot org 2006-11-18 18:20 ` amacleod at redhat dot com [this message] 2006-11-24 2:19 ` [Bug tree-optimization/29877] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2007-01-08 8:34 ` [Bug tree-optimization/29877] [4.0/4.1/4.2/4.3 " shinwell at gcc dot gnu dot org 2007-02-03 20:58 ` [Bug tree-optimization/29877] [4.0/4.1/4.2 " gdr at gcc dot gnu dot org 2007-02-03 21:03 ` pinskia at gcc dot gnu dot org 2007-02-05 5:25 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:19 ` mmitchel at gcc dot gnu dot org 2007-03-09 18:12 ` amacleod at gcc dot gnu dot org 2007-03-12 5:07 ` [Bug tree-optimization/29877] [4.0/4.1 " pinskia at gcc dot gnu dot org 2008-07-04 15:55 ` [Bug tree-optimization/29877] [4.1 " jsm28 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=20061118182006.7907.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).