Re: [PATCH 01/13] improve safety of freeing bitmaps

2017-05-10 Thread Richard Biener
On Wed, May 10, 2017 at 12:52 PM, Trevor Saunders wrote: > On Wed, May 10, 2017 at 10:14:17AM +0200, Richard Biener wrote: >> On Tue, May 9, 2017 at 10:52 PM, wrote: >> > From: Trevor Saunders >> > >> > There's two groups of changes here, first taking a sbitmap &, so that we >> > can assign nul

Re: [PATCH 01/13] improve safety of freeing bitmaps

2017-05-10 Thread Trevor Saunders
On Wed, May 10, 2017 at 10:14:17AM +0200, Richard Biener wrote: > On Tue, May 9, 2017 at 10:52 PM, wrote: > > From: Trevor Saunders > > > > There's two groups of changes here, first taking a sbitmap &, so that we > > can assign null to the pointer after freeing the sbitmap to prevent use > > aft

Re: [PATCH 01/13] improve safety of freeing bitmaps

2017-05-10 Thread Richard Biener
On Tue, May 9, 2017 at 10:52 PM, wrote: > From: Trevor Saunders > > There's two groups of changes here, first taking a sbitmap &, so that we > can assign null to the pointer after freeing the sbitmap to prevent use > after free through that pointer. Second we define overloads of > sbitmap_free

[PATCH 01/13] improve safety of freeing bitmaps

2017-05-09 Thread tbsaunde+gcc
From: Trevor Saunders There's two groups of changes here, first taking a sbitmap &, so that we can assign null to the pointer after freeing the sbitmap to prevent use after free through that pointer. Second we define overloads of sbitmap_free and bitmap_free taking auto_sbitmap and auto_bitmap r