public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gonzalez.rulez at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63692] Temporary object stack space is not re-used
Date: Fri, 31 Oct 2014 15:12:00 -0000	[thread overview]
Message-ID: <bug-63692-4-6uacKHfRhK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63692-4@http.gcc.gnu.org/bugzilla/>

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.


      parent reply	other threads:[~2014-10-31 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 21:43 [Bug c++/63692] New: " gonzalez.rulez at gmail dot com
2014-10-30 23:29 ` [Bug c++/63692] " pinskia at gcc dot gnu.org
2014-10-31  9:49 ` rguenth at gcc dot gnu.org
2014-10-31 15:12 ` gonzalez.rulez at gmail dot com [this message]

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=bug-63692-4-6uacKHfRhK@http.gcc.gnu.org/bugzilla/ \
    --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).