This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Linking libgfortran with libiberty

From: FX <fxcoudert at gmail dot com>
To: Paolo Bonzini <bonzini at gnu dot org>
Cc: Jakub Jelinek <jakub at redhat dot com>, fortran at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Mon, 30 Mar 2009 15:18:54 +0200
Subject: Re: Linking libgfortran with libiberty
References: <6BA6A458-3B25-4186-ADD6-C2956BBF13A9@gmail.com> <20090329223207.GP16681@sunsite.ms.mff.cuni.cz> <49D0B2A7.5030407@gnu.org>

+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 our proposal. I can understand that you have objections based on licence issues to make to that patch, but I'm sure the gfortran maintainers are the best people to make the decision of whether this patch is a good thing for the project (and much demanded by the community); they have already made that choice, so we should focus on talking about how to work around the current licence issue.

FX

Follow-Ups:
- Re: Linking libgfortran with libiberty
  - From: Paolo Bonzini

References:
- Linking libgfortran with libiberty
  - From: FX
- Re: Linking libgfortran with libiberty
  - From: Jakub Jelinek
- Re: Linking libgfortran with libiberty
  - From: Paolo Bonzini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]