From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: larsi@gnus.org, 58509@debbugs.gnu.org
Subject: bug#58509: 29.0.50; Synchronous nativecomp
Date: Wed, 19 Oct 2022 22:11:33 +0300 [thread overview]
Message-ID: <838rlbzl0a.fsf@gnu.org> (raw)
In-Reply-To: <xjfv8of7i1o.fsf@ma.sdf.org> (message from Andrea Corallo on Wed, 19 Oct 2022 19:02:59 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: larsi@gnus.org, 58509@debbugs.gnu.org
> Date: Wed, 19 Oct 2022 19:02:59 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andrea Corallo <akrl@sdf.org>
> >> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 58509@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.
next prev parent reply other threads:[~2022-10-19 19:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:38 bug#58509: 29.0.50; Synchronous nativecomp Lars Ingebrigtsen
2022-10-14 10:53 ` Eli Zaretskii
2022-10-14 10:56 ` Lars Ingebrigtsen
2022-10-14 11:04 ` Eli Zaretskii
2022-10-14 11:13 ` Lars Ingebrigtsen
2022-10-14 11:49 ` Eli Zaretskii
2022-10-14 11:51 ` Lars Ingebrigtsen
2022-10-14 11:53 ` Eli Zaretskii
2022-10-14 11:59 ` Lars Ingebrigtsen
2022-10-14 12:11 ` Eli Zaretskii
2022-10-14 12:20 ` Lars Ingebrigtsen
2022-10-14 12:54 ` Eli Zaretskii
2022-10-14 12:59 ` Lars Ingebrigtsen
2022-10-14 13:05 ` Eli Zaretskii
2022-10-14 13:15 ` Lars Ingebrigtsen
2022-10-14 21:40 ` Andrea Corallo
2022-10-15 6:45 ` Eli Zaretskii
2022-10-15 9:22 ` Lars Ingebrigtsen
2022-10-15 16:29 ` Andrea Corallo
2022-10-16 8:50 ` Lars Ingebrigtsen
2022-10-17 7:52 ` Andrea Corallo
2022-10-17 11:20 ` Lars Ingebrigtsen
2022-10-17 11:57 ` Lars Ingebrigtsen
2022-10-17 13:41 ` Eli Zaretskii
2022-10-17 19:30 ` Lars Ingebrigtsen
2022-10-18 13:43 ` Eli Zaretskii
2022-10-18 13:55 ` Andrea Corallo
2022-10-18 18:15 ` Lars Ingebrigtsen
2022-10-19 19:06 ` Andrea Corallo
2022-10-18 18:45 ` Eli Zaretskii
2022-10-19 19:02 ` Andrea Corallo
2022-10-19 19:11 ` Eli Zaretskii [this message]
2022-10-19 19:31 ` Andrea Corallo
2022-10-20 6:43 ` Eli Zaretskii
2022-10-20 7:23 ` Andrea Corallo
2022-10-20 8:06 ` Eli Zaretskii
2022-10-23 10:51 ` Andrea Corallo
2022-10-23 11:43 ` Eli Zaretskii
2022-10-23 12:10 ` Andrea Corallo
2022-10-25 19:54 ` Andrea Corallo
2022-10-26 2:30 ` Eli Zaretskii
2022-10-26 6:40 ` Andrea Corallo
2022-10-18 18:14 ` Lars Ingebrigtsen
2022-10-18 18:32 ` Eli Zaretskii
2022-10-18 18:39 ` Eli Zaretskii
2022-10-19 9:06 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rlbzl0a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58509@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).