> For Windows, I found
> http://www.codeproject.com/KB/applications/visualleakdetector.aspx which
> is free (LGPL); I don't know how good it is and it may be hard to
> compile it to GCC, but doing that would be a better service than adding
> a leak detector to libgfortran (Purify is proprietary an
FX wrote:
>> +1. If libgfortran includes a custom allocator of any sort (does it?)
>> instead of using malloc/free, it should use valgrind hooks like those we
>> already have in GCC.
>
> libgfortran uses malloc/free.
>
> Regarding valgrind, it's not supported on all GCC targets, so it's not a
>
+1. If libgfortran includes a custom allocator of any sort (does it?)
instead of using malloc/free, it should use valgrind hooks like
those we
already have in GCC.
libgfortran uses malloc/free.
Regarding valgrind, it's not supported on all GCC targets, so it's not
a valid alternative to o
Jakub Jelinek wrote:
> On Sun, Mar 29, 2009 at 01:00:50PM +0200, FX wrote:
>> This mail is a request for some help from our local build machinery
>> experts... We have a patch under testing for libgfortran to add
>> runtime memleaks checking, and it uses libiberty's hash tables. So, we
>> now
On Sun, Mar 29, 2009 at 01:00:50PM +0200, FX wrote:
> This mail is a request for some help from our local build machinery
> experts... We have a patch under testing for libgfortran to add
> runtime memleaks checking, and it uses libiberty's hash tables. So, we
> now link gfortran programs wit
Richard,
On 29 Mar 2009, at 12:08, Richard Guenther wrote:
On Sun, Mar 29, 2009 at 1:00 PM, FX wrote:
Hi all,
This mail is a request for some help from our local build machinery
experts... We have a patch under testing for libgfortran to add
runtime
memleaks checking, and it uses libiberty
If you wish to use particular files from libiberty in a runtime
library,
you'll need FSF approval to distribute them under GPL + exception
I'm interested only in include/hashtab.h and libiberty/hashtab.c,
which are both currently under GPL2. How does one ask for FSF approval
to distribute
On Sun, 29 Mar 2009, Richard Guenther wrote:
> I see that libgfortran is GPLv2 + exception while libiberty is LGPLv2. I
> think
> for statically linking libiberty into libgfortran there may be issues.
The license situation for libiberty is much more complicated than that;
parts are GPL (no exc
On Sun, Mar 29, 2009 at 1:00 PM, FX wrote:
> Hi all,
>
> This mail is a request for some help from our local build machinery
> experts... We have a patch under testing for libgfortran to add runtime
> memleaks checking, and it uses libiberty's hash tables. So, we now link
> gfortran programs with
Hi all,
This mail is a request for some help from our local build machinery
experts... We have a patch under testing for libgfortran to add
runtime memleaks checking, and it uses libiberty's hash tables. So, we
now link gfortran programs with libiberty. We also need to link in
libiberty w
10 matches
Mail list logo
