GNU bug report logs - #58509
29.0.50; Synchronous nativecomp

Previous Next

Full log

Message #110 received at 58509 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: larsi <at> gnus.org, 58509 <at> debbugs.gnu.org
Subject: Re: bug#58509: 29.0.50; Synchronous nativecomp
Date: Wed, 19 Oct 2022 22:11:33 +0300

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: larsi <at> gnus.org, 58509 <at> debbugs.gnu.org
> Date: Wed, 19 Oct 2022 19:02:59 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Andrea Corallo <akrl <at> sdf.org>
> >> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 58509 <at> debbugs.gnu.org
> >> Date: Tue, 18 Oct 2022 13:55:18 +0000
> >> 
> >> The attached works for me for fixing the trampoline issue (unless I did
> >> something wrong reproducing).
> >> 
> >> I named the flag -no-comp-spawn from the variable it controls.  Happy to
> >> rename it if we have something better, but being for internal use only
> >> maybe is already okay?
> >
> > On second thought: why do we need a special knob for that?  Could we
> > instead _always_ compile trampolines "without spawning" in a --batch
> > session?
> 
> Hi Eli,
> 
> unfortunately we cannot as libgccjit leaks memory :/

I think there could be a misunderstanding here.  What I meant is to do
whatever we do under -no-comp-spawn, but do it always for trampolines
in the --batch invocations, without the need to see -no-comp-spawn on
the command line.

Or maybe I misunderstand what -no-comp-spawn does, in which case can
you tell me what I missed?

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.