From: Jeff Law <law@redhat.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: "gcc@gnu.org" <gcc@gnu.org>
Subject: Re: Leaking bitmap data in ree.c?
Date: Mon, 21 Mar 2016 17:13:00 -0000 [thread overview]
Message-ID: <56F02BA3.3090600@redhat.com> (raw)
In-Reply-To: <20160321171530.GA27540@ball>
On 03/21/2016 11:15 AM, Trevor Saunders wrote:
>
>> I'll resist the urge for now to apply RAII principles in this code, but
>> that'd probably a much cleaner way to think about the problem in general.
>
> I worked on a couple attempts to c++ify bitmaps a while back, but never
> finished any of them, but I could probably publish what I did in case
> someone wants to pick that up for gcc 7.
Can't hurt.
FWIW, bitmaps are low level and independent of trees, rtl, etc that we
ought to (in theory) be able to class-ify them and build a real unit
testing framework for them.
jeff
next prev parent reply other threads:[~2016-03-21 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 19:18 Jeff Law
2016-03-21 3:22 ` Trevor Saunders
2016-03-21 16:42 ` Jeff Law
2016-03-21 17:10 ` Trevor Saunders
2016-03-21 17:13 ` Jeff Law [this message]
2016-03-21 17:17 ` David Malcolm
2016-03-21 17:20 ` Jeff Law
2016-03-22 9:29 ` Richard Biener
2016-04-03 0:45 ` Trevor Saunders
2016-04-03 0:53 ` Trevor Saunders
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=56F02BA3.3090600@redhat.com \
--to=law@redhat.com \
--cc=gcc@gnu.org \
--cc=tbsaunde@tbsaunde.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).