public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mitya57 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65434] Memory leak in pool constructor
Date: Mon, 16 Mar 2015 15:33:00 -0000 [thread overview]
Message-ID: <bug-65434-4-efo78Qmjex@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65434-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434
--- Comment #2 from Dmitry Shachnev <mitya57 at gmail dot com> ---
Will anything bad happen if that memory is freed in the destructor?
For me, the issue is mostly aesthetic — I got used to not seeing any Valgrind
warnings in my programs :)
>From gcc-bugs-return-480468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 16 15:42:51 2015
Return-Path: <gcc-bugs-return-480468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3125 invoked by alias); 16 Mar 2015 15:42:51 -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 3063 invoked by uid 48); 16 Mar 2015 15:42:48 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37303] const compound initializers in structs are written to .data instead of .rodata
Date: Mon, 16 Mar 2015 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.3.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
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: bug_status cc resolution
Message-ID: <bug-37303-4-0Jfki5fNif@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37303-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: 2015-03/txt/msg01612.txt.bz2
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id7303
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mpolacek at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This one should be fixed.
next prev parent reply other threads:[~2015-03-16 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 11:03 [Bug libstdc++/65434] New: " mitya57 at gmail dot com
2015-03-16 15:09 ` [Bug libstdc++/65434] " redi at gcc dot gnu.org
2015-03-16 15:33 ` mitya57 at gmail dot com [this message]
2015-03-16 16:00 ` redi 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-65434-4-efo78Qmjex@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).