This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: Custom malloc fails after gcc-5.x due to changes in eh_alloc.cc
- From: Kaushik Phatak <Kaushik dot Phatak at kpit dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 27 Mar 2017 04:23:38 +0000
- Subject: RE: Custom malloc fails after gcc-5.x due to changes in eh_alloc.cc
- Authentication-results: sourceware.org; auth=none
- Authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=kpit.com;
- References: <BMXPR01MB07272E7CFCBAEFD0E0AAF92CFC3F0@BMXPR01MB0727.INDPRD01.PROD.OUTLOOK.COM> <CAH6eHdTxZ_tTeMDUY4=-LKnAiPDFEJnboP4DkwK-hDe2=ErkyQ@mail.gmail.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hi,
Thanks for your quick reply, much appreciated!
>> The uncommitted patch at https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01158.html
We have looked at this patch.
Though we do build the toolchain often, we may not be able to integrate this patch
as-is in our gcc-5.3.0 sources due to other dependencies like "__freeres()".
Additionally, it would also require to pass '-std=c++11' to our build environment
as other dependencies use c++11 keywords.
>> Why can't you call the init function on the first call to malloc? For example,
>> using a local static variable:
We will look into this possibility as well.
Thanks!
Best Regards,
Kaushik
-----Original Message-----
From: Jonathan Wakely [mailto:jwakely.gcc@gmail.com]
Sent: Thursday, March 23, 2017 5:16 PM
To: Kaushik Phatak <Kaushik.Phatak@kpit.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Custom malloc fails after gcc-5.x due to changes in eh_alloc.cc
On 23 March 2017 at 11:32, Kaushik Phatak wrote:
> Hi,
> One of our application uses its own custom malloc implementation.