public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19662] [FEATURE REQUEST] Need an option preventing any atexit object destructions
Date: Fri, 28 Jan 2005 07:17:00 -0000	[thread overview]
Message-ID: <20050128071750.6151.qmail@sourceware.org> (raw)
In-Reply-To: <20050128052304.19662.yuri@tsoft.com>


------- Additional Comments From gdr at integrable-solutions dot net  2005-01-28 07:17 -------
Subject: Re:  New: [FEATURE REQUEST] Need an option preventing any atexit object destructions

"yuri at tsoft dot com" <gcc-bugzilla@gcc.gnu.org> writes:

| For ex. "gcc -no-atexit ..." will avoid any post-run object destructions.
| 
| This feature is very useful: if I have very performance critical application and
| all my objects are simple and do not *really* require destructions I may opt for
| this. Benefit: will be less extra stuff inserted by compiler and program will
| run faster with better optimizations.
| 
| And often people do not destroy objects anyways.

If your objects are simple and do not need destruction, just don't
define destructors.

-- Gaby


-- 


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


  reply	other threads:[~2005-01-28  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28  5:23 [Bug c++/19662] New: " yuri at tsoft dot com
2005-01-28  7:17 ` gdr at integrable-solutions dot net [this message]
2005-01-28 14:00 ` [Bug c++/19662] " pinskia at gcc dot gnu dot org
2005-01-28 20:54 ` yuri at tsoft dot com
2005-01-28 22:42 ` gdr at integrable-solutions dot net

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=20050128071750.6151.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).