public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51060] Temporary object stack space is not re-used Date: Wed, 09 Nov 2011 14:46:00 -0000 [thread overview] Message-ID: <bug-51060-4-2DCDAPNmYO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51060-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51060 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011-11-09 CC| |jason at redhat dot com, | |matz at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-09 14:41:24 UTC --- Confirmed. The new death-point stuff doesn't help as the frontend does not seem to construct scopes properly for this testcase. ;; Function void Test() (null) ;; enabled by -tree-original <<cleanup_point <<< Unknown tree: expr_stmt (void) TARGET_EXPR <D.21343, <<< Unknown tree: aggr_init_expr 4 __comp_ctor D.21343 0B >>>> >>>>>; <<cleanup_point <<< Unknown tree: expr_stmt (void) TARGET_EXPR <D.21344, <<< Unknown tree: aggr_init_expr 4 __comp_ctor D.21344 0B >>>> >>>>>; ...
next prev parent reply other threads:[~2011-11-09 14:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-09 14:11 [Bug c++/51060] New: " andvgal at gmail dot com 2011-11-09 14:46 ` rguenth at gcc dot gnu.org [this message] 2011-11-11 21:57 ` [Bug c++/51060] " jason at gcc dot gnu.org 2011-11-13 1:20 ` jason at gcc dot gnu.org 2011-11-13 2:06 ` jason at gcc dot gnu.org
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-51060-4-2DCDAPNmYO@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: linkBe 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).