From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6180 invoked by alias); 28 Jan 2005 07:17:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 6152 invoked by alias); 28 Jan 2005 07:17:50 -0000 Date: Fri, 28 Jan 2005 07:17:00 -0000 Message-ID: <20050128071750.6151.qmail@sourceware.org> From: "gdr at integrable-solutions dot net" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050128052304.19662.yuri@tsoft.com> References: <20050128052304.19662.yuri@tsoft.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/19662] [FEATURE REQUEST] Need an option preventing any atexit object destructions X-Bugzilla-Reason: CC X-SW-Source: 2005-01/txt/msg04128.txt.bz2 List-Id: ------- 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" 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