On Thu, Aug 23, 2012 at 11:24:26AM +0200, Richard Guenther wrote:
> > Perhaps it would make sense to commit the fortran/ change separately to fix
> > the leak in there, and resolve the rest in a follow-up when it is clear what
> > to do in the C++ FE.
>
> Yes. Does the copy_node change pass testi
On Thu, Aug 23, 2012 at 9:45 AM, Jakub Jelinek wrote:
> On Wed, Aug 22, 2012 at 03:29:28PM +0200, Richard Guenther wrote:
>> On Wed, Aug 22, 2012 at 3:03 PM, Jakub Jelinek wrote:
>> > init_function_start is these days supposed to be called only at the start
>> > of
>> > RTL expansion, it shouldn
On Wed, Aug 22, 2012 at 03:29:28PM +0200, Richard Guenther wrote:
> On Wed, Aug 22, 2012 at 3:03 PM, Jakub Jelinek wrote:
> > init_function_start is these days supposed to be called only at the start of
> > RTL expansion, it shouldn't be called much earlier, because then we leak
> > e.g. the memor
On Wed, Aug 22, 2012 at 3:03 PM, Jakub Jelinek wrote:
> Hi!
>
> init_function_start is these days supposed to be called only at the start of
> RTL expansion, it shouldn't be called much earlier, because then we leak
> e.g. the memory allocated by init_emit.
>
> Bootstrapped/regtested on x86_64-lin
On 08/22/2012 03:03 PM, Jakub Jelinek wrote:
init_function_start is these days supposed to be called only at the start of
RTL expansion, it shouldn't be called much earlier, because then we leak
e.g. the memory allocated by init_emit.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for
Hi!
init_function_start is these days supposed to be called only at the start of
RTL expansion, it shouldn't be called much earlier, because then we leak
e.g. the memory allocated by init_emit.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2012-08-22 Jakub Jelinek
