public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13875] New: [tree-ssa] function not optimized
Date: Tue, 27 Jan 2004 05:11:00 -0000 [thread overview]
Message-ID: <20040127051055.13875.dann@godzilla.ics.uci.edu> (raw)
cc1plus -v
GNU C++ version 3.5-tree-ssa 20040123 (merged 20040102) (i686-pc-linux-gnu)
compiled by GNU C version 3.5-tree-ssa 20040123 (merged 20040102).
generate-3.4.ii is the famous code from PR8361
cc1plus -quiet -fpreprocessed -O2 generate-3.4.ii -fdump-tree-optimized
Looking at the function HeuristicCounters::~HeuristicCounters() in
generate-3.4.ii.t35.optimized, it seems that this function has not been
optimized, there are obvious jump threading opportunities.
It is strange that if -fno-inline is added to the command line, then
HeuristicCounters::~HeuristicCounters() is optimized!
--
Summary: [tree-ssa] function not optimized
Product: gcc
Version: tree-ssa
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dann at godzilla dot ics dot uci dot edu
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13875
next reply other threads:[~2004-01-27 5:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 5:11 dann at godzilla dot ics dot uci dot edu [this message]
2004-01-27 5:13 ` [Bug optimization/13875] " pinskia at gcc dot gnu dot org
2004-01-30 0:33 ` pinskia at gcc dot gnu dot org
2004-01-31 3:43 ` pinskia at gcc dot gnu dot org
2004-02-29 4:01 ` [Bug optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level pinskia at gcc dot gnu dot org
2004-02-29 4:09 ` pinskia at gcc dot gnu dot org
2004-03-01 3:43 ` law at gcc dot gnu dot org
2004-03-01 17:52 ` law at gcc dot gnu dot org
2004-03-01 19:51 ` giovannibajo at libero dot it
2004-03-03 18:14 ` dann at godzilla dot ics dot uci dot edu
2004-03-03 18:26 ` law at redhat dot com
2004-03-08 2:07 ` law at redhat dot com
2004-03-08 2:09 ` law at gcc dot gnu dot org
2004-03-08 23:47 ` dann at godzilla dot ics dot uci dot edu
2004-03-08 23:51 ` pinskia at gcc dot gnu dot org
2004-03-09 23:37 ` law at redhat dot com
2004-04-06 1:27 ` dann at godzilla dot ics dot uci dot edu
2004-04-06 1:44 ` pinskia at gcc dot gnu dot org
2004-04-08 22:58 ` law at redhat dot com
2004-04-08 23:36 ` dann at godzilla dot ics dot uci dot edu
2004-04-08 23:45 ` law at redhat dot com
2004-04-20 16:40 ` dann at godzilla dot ics dot uci dot edu
2004-05-27 7:54 ` [Bug tree-optimization/13875] " pinskia at gcc dot gnu dot org
2004-06-02 20:16 ` pinskia at gcc dot gnu dot org
2004-10-11 17:08 ` pinskia at gcc dot gnu dot org
2005-01-15 5:38 ` pinskia at gcc dot gnu dot org
2005-06-12 20:41 ` pinskia at gcc dot gnu dot org
2005-06-13 13:52 ` law at redhat dot com
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=20040127051055.13875.dann@godzilla.ics.uci.edu \
--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).