public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14703] [4.4 regression] Inadequate optimization of inline templated functions, infinite loop in ipa-reference and memory hog
Date: Fri, 12 Sep 2008 08:34:00 -0000 [thread overview]
Message-ID: <20080912083319.5512.qmail@sourceware.org> (raw)
In-Reply-To: <bug-14703-3016@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from hubicka at gcc dot gnu dot org 2008-09-12 08:33 -------
Having testcase would be great. In theory removing unused things from debug
info should not make any difference. Perhaps it is related to stack frame
packing, that is only other place walking blocks.
could you please try adding && is_gimple_reg (*t)?
Honza
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14703
next prev parent reply other threads:[~2008-09-12 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14703-3016@http.gcc.gnu.org/bugzilla/>
2006-03-02 20:25 ` [Bug tree-optimization/14703] Inadequate optimization of inline templated functions eric-gcc at omnifarious dot org
2006-03-03 10:29 ` rguenth at gcc dot gnu dot org
2008-09-06 12:39 ` [Bug tree-optimization/14703] [4.4 regression] Inadequate optimization of inline templated functions, infinite loop in ipa-reference and memory hog hubicka at gcc dot gnu dot org
2008-09-06 12:57 ` hubicka at gcc dot gnu dot org
2008-09-06 17:12 ` hubicka at gcc dot gnu dot org
2008-09-06 20:24 ` hubicka at gcc dot gnu dot org
2008-09-11 5:19 ` luisgpm at linux dot vnet dot ibm dot com
2008-09-12 8:34 ` hubicka at gcc dot gnu dot org [this message]
2008-09-12 8:40 ` hubicka at gcc dot gnu dot org
2008-09-19 6:23 ` hubicka at gcc dot gnu dot org
2008-11-01 11:52 ` [Bug tree-optimization/14703] " rguenth 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=20080912083319.5512.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).