Re: Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-07-07 Thread Dominique Dhumieres
In https://gcc.gnu.org/ml/fortran/2014-06/msg00150.html I wrote I am now trying to do the back port to 4.9 and I got two failures: ... Actually I did not applied the right patch, with it the testsuite pass without regression. Still OK for 4.9.1? TIA Dominique

Re: Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-07-07 Thread Paul Richard Thomas
Dear Dominique, On condition that your commit the right patch :-), OK for 4.9.1 Cheers Paul On 7 July 2014 13:48, Dominique Dhumieres domi...@lps.ens.fr wrote: In https://gcc.gnu.org/ml/fortran/2014-06/msg00150.html I wrote I am now trying to do the back port to 4.9 and I got two failures:

Re: Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-07-07 Thread Dominique Dhumieres
On condition that your commit the right patch :-), OK for 4.9.1 Indeed! Committed as r212329. Thanks for the review. Dominique

Re: Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-06-16 Thread Dominique Dhumieres
Dear Paul, Late thanks for the review, the patch has been committed to trunk at r211405. OK for trunk and, I would suggest 4.9. I am now trying to do the back port to 4.9 and I got two failures: FAIL: gfortran.dg/alloc_comp_basics_1.f90 -O* scan-tree-dump-times original builtin_free 18

Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-06-09 Thread Dominique Dhumieres
Patch posted at https://gcc.gnu.org/ml/fortran/2014-05/msg00155.html. TIA Dominique

Re: Ping [PATCH, fortran] PR 41936 Memory leakage with allocatables and user-defined operators

2014-06-09 Thread Paul Richard Thomas
Dear Dominique, Without the patch applied, trunk shows 360 bytes definitely missing in 3 blocks for the original testcase and 9 out of 92 allocs did not have corresponding frees. WIth the patch, I get: ==20527== ==20527== HEAP SUMMARY: ==20527== in use at exit: 0 bytes in 0 blocks ==20527==