public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baldrick at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30927] tree-nested creates pointless static chains and trampolines when the callgraph is non-trivial
Date: Thu, 15 Mar 2007 14:49:00 -0000	[thread overview]
Message-ID: <20070315144904.25168.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30927-13647@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from baldrick at gcc dot gnu dot org  2007-03-15 14:49 -------
Created an attachment (id=13208)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13208&action=view)
Proposed fix

Bootstraps with all languages including Ada.  Does not introduce any new
testsuite failures.  I'd appreciate it if the ACT people could pass it
through their regression test suite.  I don't know if this interacts
correctly with OMP because I don't understand OMP.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30927


  parent reply	other threads:[~2007-03-15 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 17:33 [Bug tree-optimization/30927] New: " baldrick at gcc dot gnu dot org
2007-02-22 17:40 ` [Bug tree-optimization/30927] " ebotcazou at gcc dot gnu dot org
2007-03-15 14:49 ` baldrick at gcc dot gnu dot org [this message]
2007-03-15 15:12 ` ebotcazou at gcc dot gnu dot org
2007-03-15 15:16 ` baldrick at free dot fr
2007-03-15 15:35 ` baldrick at free dot fr
2007-03-15 19:45 ` baldrick at gcc dot gnu dot org
2007-03-21  9:31 ` ebotcazou at gcc dot gnu dot org
2008-01-10 19:12 ` baldrick at gcc dot gnu dot org
2009-09-16 18:55 ` rth 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=20070315144904.25168.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: link
Be 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).