This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Leaking bitmap data in ree.c?

From: Jeff Law <law at redhat dot com>
To: Trevor Saunders <tbsaunde at tbsaunde dot org>
Cc: "gcc at gnu dot org" <gcc at gnu dot org>
Date: Mon, 21 Mar 2016 11:13:07 -0600
Subject: Re: Leaking bitmap data in ree.c?
Authentication-results: sourceware.org; auth=none
References: <56EC5478 dot 5080500 at redhat dot com> <20160321032339 dot GA24419 at ball> <56F0246A dot 5000002 at redhat dot com> <20160321171530 dot GA27540 at 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 weought to (in theory) be able to class-ify them and build a real unittesting framework for them.


jeff

Follow-Ups:
- Re: Leaking bitmap data in ree.c?
  - From: David Malcolm

References:
- Leaking bitmap data in ree.c?
  - From: Jeff Law
- Re: Leaking bitmap data in ree.c?
  - From: Trevor Saunders
- Re: Leaking bitmap data in ree.c?
  - From: Jeff Law
- Re: Leaking bitmap data in ree.c?
  - From: Trevor Saunders

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]