public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/43099] rethrowing leaks memory like a sieve Date: Sat, 08 Nov 2014 17:23:00 -0000 [thread overview] Message-ID: <bug-43099-4-2E3Fydjhmk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43099-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43099 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |fxcoudert at gcc dot gnu.org Resolution|--- |INVALID --- Comment #10 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- Either this was in the Apple unwinder, or this got fixed at some point. Current trunk on darwin14 does not give memory leaks for the testcase, neither at -m32 nor at -m64.
next parent reply other threads:[~2014-11-08 17:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43099-4@http.gcc.gnu.org/bugzilla/> 2014-11-08 17:23 ` fxcoudert at gcc dot gnu.org [this message] 2010-02-16 22:40 [Bug c++/43099] New: " dan dot colascione at gmail dot com 2010-02-16 22:40 ` [Bug target/43099] " dan dot colascione at gmail dot com 2010-02-16 22:41 ` dan dot colascione at gmail dot com 2010-02-16 22:43 ` dan dot colascione at gmail dot com 2010-02-16 22:46 ` pinskia at gcc dot gnu dot org 2010-02-16 22:47 ` dan dot colascione at gmail dot com 2010-02-16 22:47 ` pinskia at gcc dot gnu dot org 2010-02-16 23:07 ` dan dot colascione at gmail dot com 2010-02-16 23:44 ` dan dot colascione at gmail dot com 2010-02-16 23:56 ` pinskia at gcc dot gnu dot 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-43099-4-2E3Fydjhmk@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).