This is the mail archive of the
mailing list for the GCC project.
Re: [RFC PATCH] add auto_bitmap
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Trevor Saunders <tsaunders at mozilla dot com>
- Cc: Jeff Law <law at redhat dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 15 Nov 2013 12:11:07 +0100
- Subject: Re: [RFC PATCH] add auto_bitmap
- Authentication-results: sourceware.org; auth=none
- References: <1384427080-13613-1-git-send-email-tsaunders at mozilla dot com> <5285342D dot 3050505 at redhat dot com> <9ee1bb00-910a-4a77-bfdf-dce8515c1a87 at email dot android dot com> <5285418C dot 3090008 at redhat dot com> <CAFiYyc0fguEMv3g6Ker2=ddzdXiJHV7cnOiPA0TJCf4phdrHtQ at mail dot gmail dot com> <20131115103720 dot GB17612 at tsaunders-iceball dot corp dot tor1 dot mozilla dot com>
On Fri, Nov 15, 2013 at 11:37 AM, Trevor Saunders <email@example.com> wrote:
> On Fri, Nov 15, 2013 at 10:56:24AM +0100, Richard Biener wrote:
>> On Thu, Nov 14, 2013 at 10:33 PM, Jeff Law <firstname.lastname@example.org> wrote:
>> > On 11/14/13 14:14, Richard Biener wrote:
>> >>> I'm just pointed out that of all the stuff you changed, these were the
>> >>> only ones I saw where lifetimes were changed significantly.
>> >> I still ask why we need a new type and cannot put this functionality into
>> >> bitmap_head itself.
>> > Given that bitmap is just a *bitmap_head_def aren't we suggesting the same
>> > thing?
>> Not sure - I thought Trevor wanted to make auto_bitmap a full C++ thing,
>> not bitmap itself?
> My only firm goals are less manual memory management, and moving the
> bitmap_head bit onto the stack would be really nice. I'd also like to
> leave bitmaps allocated in gc memory alone for the time being, but those
> are the only firm goals. I'm currently trying the approach of adding
> constructors and destructors to bitmap_head, but apparently something is
> causing them to get invoked even when everybody deals with bitmap_head *
> which leads to ICEs that I'm investigating now.
They are used embedded into other structures as well (to avoid a
>> > jeff