From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18129 invoked by alias); 28 Feb 2003 01:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18111 invoked by uid 71); 28 Feb 2003 01:56:01 -0000 Date: Fri, 28 Feb 2003 01:56:00 -0000 Message-ID: <20030228015601.18110.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Sandor Kovacs Subject: Re: c++/9872: temporary destructor not called? Reply-To: Sandor Kovacs X-SW-Source: 2003-02/txt/msg01468.txt.bz2 List-Id: The following reply was made to PR c++/9872; it has been noted by GNATS. From: Sandor Kovacs To: Wolfgang Bangerth Cc: gcc-bugs@gcc.gnu.org, , Subject: Re: c++/9872: temporary destructor not called? Date: Fri, 28 Feb 2003 01:54:43 +0000 Ok, standalone, no library dependent test code is here: I've basically stripped down the QT QString implementation. Compile: - to eat up memory: g++ -c bug.cpp g++ bug.o -o bug - works properly: g++ -fno-elide-constructors -c bug.cpp g++ bug.o -o bug Find .cpp, .ii, .s attached: bug.without-felide.s is the one which eats up memory, the other one bug.with-felide.s is the properly working one. If this is indeed a bug in gcc then if would explain why I have increasing swap usage after running KDE for weeks, even thoug no app. is running. In such cases I to restart KDE and swap usage disappeares. IF indeed it is a gcc bug and SuSE compiled kde using gcc3.2... Regards, Sandor > Sandor, > I attached your preprocessed source. Thanks for sending them in. > However... > > > If I've missed something or you need further info please let me know; > > ...yes, we are missing something: > > gcc -L/usr/lib/qt3/lib -lqt-mt bug.o -o bug > > You are linking with libqt-mt.so. What we need is a _self-contained_ > testcase, i.e. something that we can test without additional libraries. If > we don't have that, it is impossible to find out whether the problem is in > the compiler itself, or in the code that is in the library that is being > linked in. > > Please try to pack everything into one file, including the necessary .cpp > files from qt, such that it can be compiled without linking together > several .o or .so files. > > Thanks > Wolfgang