[Bug c++/63692] New: Temporary object stack space is not re-used

[Bug c++/63692] New: Temporary object stack space is not re-used

[gonzalez.rulez at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63692

            Bug ID: 63692
           Summary: Temporary object stack space is not re-used
           Product: gcc
           Version: 4.8.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gonzalez.rulez at gmail dot com

Created attachment 33849
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33849&action=edit
The same test case as in 51060

Related to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51060

The only difference between this issue and 51060 is that code is being compiled
without "Os".

$ g++ -c 51060.cpp -Wframe-larger-than=2048 -Werror
51060.cpp: In function ‘void Test()’:
51060.cpp:37:1: error: the frame size of 10240 bytes is larger than 2048 bytes
[-Werror=frame-larger-than=]
 }
 ^
cc1plus: all warnings being treated as errors
See attached code sample.

Environment:

$ g++ -v
Using built-in specs.
COLLECT_GCC=/usr/bin/g++
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.3/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin
--enable-initfini-array --enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-isl=/builddir/build/BUILD/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/isl-install
--with-cloog=/builddir/build/BUILD/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/cloog-install
--with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC)

$ uname -s -r -v -p -i -o
Linux 3.16.6-200.fc20.x86_64 #1 SMP Wed Oct 15 13:06:51 UTC 2014 x86_64 x86_64
GNU/Linux
>From gcc-bugs-return-465400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 30 21:43:14 2014
Return-Path: <gcc-bugs-return-465400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20680 invoked by alias); 30 Oct 2014 21:43:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20640 invoked by uid 48); 30 Oct 2014 21:43:08 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63691] GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Date: Thu, 30 Oct 2014 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63691-4-3EsIGV91VS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63691-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63691-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-10/txt/msg02421.txt.bz2
Content-length: 402

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc691

--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
I don't see how that change could possibly cause the kind of failures you're
showing.  It's got to be something else.

I would also strongly suggest trying with the latest gcc-4.9.x release as Jakub
has bundled many fixes into those point releases since gcc-4.9 was initially
released.

[Bug c++/63692] Temporary object stack space is not re-used

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63692

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Yes -O0 does not reuse temp object space at all and that is by design for speed
reasons.

[Bug c++/63692] Temporary object stack space is not re-used

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63692

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
for compile-time speed.

[Bug c++/63692] Temporary object stack space is not re-used

[gonzalez.rulez at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63692

--- Comment #3 from Gonzalez Pedro <gonzalez.rulez at gmail dot com> ---
Ok. We are affected by this in the debug builds which are built without any
optimizations. Reviewing -O2 options I didn't find an option, which enables or
disables reuse of temp object space. Is there one?

P.S.
On the other hand this is not an issue with POD types.