public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19661] unnecessary atexit calls emitted for static objects with empty destructors
Date: Wed, 20 Feb 2008 21:53:00 -0000	[thread overview]
Message-ID: <20080220215237.19116.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19661-6649@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from pinskia at gcc dot gnu dot org  2008-02-20 21:52 -------
(In reply to comment #7)
> Why do you think the front-end doesn't know that the destructor is empty? 

Because it is non trivial.  Try it with a more complex case where you have
multiple layer destructors and inlining, you will see that the front-end does
not know if it is empty until way after inlining.

-- Pinski


-- 


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


       reply	other threads:[~2008-02-20 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19661-6649@http.gcc.gnu.org/bugzilla/>
2008-02-20 21:53 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-19661-4@http.gcc.gnu.org/bugzilla/>
2021-09-24  7:41 ` antoshkka at gmail dot com
2022-11-02 15:47 ` pinskia at gcc dot gnu.org
2022-11-02 15:53 ` redi at gcc dot gnu.org
2022-11-02 17:16 ` redi at gcc dot gnu.org
2024-03-15 22:56 ` pinskia at gcc dot gnu.org
2024-03-15 23:40 ` pinskia at gcc dot gnu.org
2024-03-16  2:17 ` pinskia at gcc dot gnu.org
2024-03-16 22:47 ` i at maskray dot me
2024-04-19  0:39 ` pinskia at gcc dot gnu.org
2024-04-19  0:59 ` pinskia at gcc dot gnu.org
2024-05-07 21:47 ` cvs-commit at gcc dot gnu.org
2024-05-07 21:47 ` pinskia at gcc dot gnu.org
2005-01-27 22:24 [Bug c++/19661] New: many redundant atexit calls emitted into the executable " yuri at tsoft dot com
2005-09-24 17:43 ` [Bug tree-optimization/19661] unnecessary atexit calls emitted " 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=20080220215237.19116.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).