Re: [patch, fortran] Fix for PR 47676

2015-01-05 Thread Thomas Koenig
Am 05.01.2015 um 19:55 schrieb H.J. Lu: > On Linux/x86, I got > > ../../src-trunk/gcc/fortran/frontend-passes.c: In function ‘int > realloc_string_callback(gfc_code**, int*, void*)’: > ../../src-trunk/gcc/fortran/frontend-passes.c:152:38: error: > ‘gfc_discard_nops’ was not declared in this scope

Re: [patch, fortran] Fix for PR 47676

2015-01-05 Thread H.J. Lu
On Mon, Dec 29, 2014 at 4:25 PM, Thomas Koenig wrote: > Hello world, > > this patch fixes the long-standing bug. A missing temporary > causes an invalid read in realloc_on_assign_5.f03 which > only becomes noticable when setting MALLOC_CHECK_ or when > using valgrind. The bug has three duplicate

Re: *ping* [patch, fortran] Fix for PR 47676

2015-01-05 Thread Marek Polacek
On Mon, Jan 05, 2015 at 12:51:55PM +0100, Thomas Koenig wrote: > Am 30.12.2014 um 01:25 schrieb Thomas Koenig: > > Hello world, > > > > this patch fixes the long-standing bug. A missing temporary > > causes an invalid read in realloc_on_assign_5.f03 which > > only becomes noticable when setting M

*ping* [patch, fortran] Fix for PR 47676

2015-01-05 Thread Thomas Koenig
Am 30.12.2014 um 01:25 schrieb Thomas Koenig: > Hello world, > > this patch fixes the long-standing bug. A missing temporary > causes an invalid read in realloc_on_assign_5.f03 which > only becomes noticable when setting MALLOC_CHECK_ or when > using valgrind. The bug has three duplicates in the

[patch, fortran] Fix for PR 47676

2014-12-29 Thread Thomas Koenig
Hello world, this patch fixes the long-standing bug. A missing temporary causes an invalid read in realloc_on_assign_5.f03 which only becomes noticable when setting MALLOC_CHECK_ or when using valgrind. The bug has three duplicates in the data base, so people keep stumbling across this. I have