public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19661] unnecessary atexit calls emitted for static objects with empty destructors
Date: Fri, 28 Jan 2005 19:11:00 -0000	[thread overview]
Message-ID: <20050128191132.26603.qmail@sourceware.org> (raw)
In-Reply-To: <20050127222428.19661.yuri@tsoft.com>


------- Additional Comments From bangerth at dealii dot org  2005-01-28 19:11 -------
Why do you think the front-end doesn't know that the destructor is empty? 
It sees its definition, and it knows about potential destructors of 
member objects and base classes, so it should have all the information. 
That being said, I don't consider this to be such an important case as 
to pour a lot of passion into this discussion :-) 
 
W. 

-- 


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


  parent reply	other threads:[~2005-01-28 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 22:24 [Bug c++/19661] New: many redundant atexit calls emitted into the executable " yuri at tsoft dot com
2005-01-28  1:08 ` [Bug c++/19661] unnecessary atexit calls emitted " bangerth at dealii dot org
2005-01-28  1:22 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org
2005-01-28  1:26 ` [Bug c++/19661] " yuri at tsoft dot com
2005-01-28  1:46 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org
2005-01-28 17:02 ` [Bug c++/19661] " bangerth at dealii dot org
2005-01-28 18:53 ` [Bug middle-end/19661] " pinskia at gcc dot gnu dot org
2005-01-28 19:11 ` bangerth at dealii dot org [this message]
2005-09-24 17:43 ` [Bug tree-optimization/19661] " 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=20050128191132.26603.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).