On 01/30/2013 11:27 AM, Ian Romanick wrote:
From: Ian Romanick
Previously the loop_state was allocated in the loop_analysis
constructor, but not freed in the (nonexistent) destructor. Moving
the allocation of the loop_state makes this code appear less sketchy.
Either way, there is no actual l
On Wed, Jan 30, 2013 at 11:27 AM, Ian Romanick wrote:
> From: Ian Romanick
>
> Previously the loop_state was allocated in the loop_analysis
> constructor, but not freed in the (nonexistent) destructor. Moving
> the allocation of the loop_state makes this code appear less sketchy.
>
> Either way,
From: Ian Romanick
Previously the loop_state was allocated in the loop_analysis
constructor, but not freed in the (nonexistent) destructor. Moving
the allocation of the loop_state makes this code appear less sketchy.
Either way, there is no actual leak. The loop_state is freed by the
single ca