public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/39839] [4.3/4.4/4.5 regression] loop invariant motion causes stack spill Date: Wed, 22 Apr 2009 13:39:00 -0000 [thread overview] Message-ID: <20090422133934.29386.qmail@sourceware.org> (raw) In-Reply-To: <bug-39839-17592@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2009-04-22 13:39 ------- Vlad, with YARA you had implemented rematerialization, right? How difficult is it to do the same with IRA for cases like this? -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at redhat dot com Priority|P3 |P2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39839
next prev parent reply other threads:[~2009-04-22 13:39 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-21 18:27 [Bug regression/39839] New: " alexvod at google dot com 2009-04-22 9:40 ` [Bug tree-optimization/39839] " rguenth at gcc dot gnu dot org 2009-04-22 13:39 ` rguenth at gcc dot gnu dot org [this message] 2009-04-22 20:37 ` vmakarov at redhat dot com 2009-05-20 14:17 ` ramana at gcc dot gnu dot org 2009-06-15 16:26 ` bonzini at gnu dot org 2009-06-22 16:29 ` steven at gcc dot gnu dot org 2009-08-04 12:49 ` rguenth at gcc dot gnu dot org 2010-01-02 0:50 ` steven at gcc dot gnu dot org 2010-01-02 11:18 ` rguenth at gcc dot gnu dot org 2010-05-22 18:32 ` [Bug tree-optimization/39839] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-06-22 16:27 ` sandra at codesourcery dot com 2010-06-22 17:29 ` bonzini at gnu dot org 2010-06-22 18:02 ` sandra at codesourcery dot com 2010-07-11 1:22 ` sandra at codesourcery dot com 2010-07-13 16:14 ` sandra at codesourcery dot com 2010-07-23 2:18 ` sandra 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=20090422133934.29386.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).