public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jh at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15345] [3.4 Regression] [non-unit-at-a-time] unreferenced nested inline functions not optimized away
Date: Sun, 13 Jun 2004 14:13:00 -0000 [thread overview]
Message-ID: <20040613141310.4475.qmail@sourceware.org> (raw)
In-Reply-To: <20040509172606.15345.dank@kegel.com>
------- Additional Comments From jh at suse dot cz 2004-06-13 14:13 -------
Subject: Re: [3.4 Regression] [non-unit-at-a-time] unreferenced nested inline functions not optimized away
>
> ------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-06-12 22:05 -------
> Jan, please investigate this problem. There are a lot of unit-at-a-time related
> regressions targeted at 3.4.1; please look at all of them and indicate your
> thoughts.
I am still offline till day after tomorrow but I will look into that
afterwards.
The irritating thing about this testcase is that nested functions bypass
cgraph code completely on GCC before tree-ssa merge and thus it does not
deffer and elliminate it.
I am quite surprised that this used to be working on 2.95 and 3.2. To
get it back I guess I will need to add some hacks into the frontend to
ask the cgraph about the reachability.
Honza
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15345
next prev parent reply other threads:[~2004-06-13 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 17:26 [Bug optimization/15345] New: " dank at kegel dot com
2004-05-09 18:59 ` [Bug optimization/15345] [3.4/3.5 Regression] [non-unit-at-a-time] " pinskia at gcc dot gnu dot org
2004-06-12 22:05 ` [Bug middle-end/15345] [3.4 " mmitchel at gcc dot gnu dot org
2004-06-13 14:13 ` jh at suse dot cz [this message]
2004-06-21 17:47 ` hubicka at gcc dot gnu dot org
2004-06-21 21:22 ` mmitchel at gcc dot gnu dot org
2004-07-02 20:47 ` pinskia at gcc dot gnu dot org
2004-07-09 16:48 ` pinskia at gcc dot gnu dot org
2004-07-19 14:11 ` jakub at gcc dot gnu dot org
2004-07-19 15:44 ` jh at suse dot cz
2004-07-21 7:37 ` cvs-commit at gcc dot gnu dot org
2004-07-21 7:39 ` cvs-commit at gcc dot gnu dot org
2004-07-21 17:54 ` pinskia 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=20040613141310.4475.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).