From: Pip Cet <pipcet@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mwd@md5i.com, 46502@debbugs.gnu.org, akrl@sdf.org
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Fri, 19 Feb 2021 13:31:49 +0000 [thread overview]
Message-ID: <CAOqdjBf-NmpQjVxaX=HB+geNbDXd9EnwWzgenQMPqo78vsQFnQ@mail.gmail.com> (raw)
In-Reply-To: <83h7m95tt2.fsf@gnu.org>
On Thu, Feb 18, 2021 at 2:33 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Pip Cet <pipcet@gmail.com>
> > Date: Thu, 18 Feb 2021 10:14:24 +0000
> > Cc: Michael Welsh Duggan <mwd@md5i.com>, 46502@debbugs.gnu.org
> >
> > One thing I've noticed in my experiments is that many builds that are
> > interrupted at the wrong point and then resumed produce different
> > results. I.e. you type "make", then hit Ctrl-C at the wrong time, then
> > type "make" again and you get a different result.
>
> What does "different result" mean in this case? is the produced .eln
> file different? or something else?
There are differences both in the .elc and .eln, and I saw different
success/failure behavior but only with local modifications. It's
possible that this is all harmless, but I have the bad habit of
assuming I can just type "make" again and have it resume an
interrupted build, and that certainly does not work on the native-comp
branch (I'm not sure it works on the master branch).
Note that all this is in serial builds. That parallelized builds are
unpredictable is a different issue entirely.
> > BTW, I'm also seeing very deep recursion when building the nativecomp
> > branch
> How do you see that?
Stack overflows in a limited-stack environment, even with the GC code
modified to allocate stack space more efficiently.
> And what code recurses so deeply?
Unfortunately, the environment I'm playing with doesn't have very good
backtrace facilities. (This is WebAssembly run by the Mozilla jsshell,
which has a small-ish stack size limit. I'll try finding what limits
the reported backtrace depth and disabling it.)
next prev parent reply other threads:[~2021-02-19 13:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 5:05 bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure Michael Welsh Duggan
2021-02-18 9:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 10:14 ` Pip Cet
2021-02-18 10:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 14:34 ` Eli Zaretskii
2021-02-19 13:31 ` Pip Cet [this message]
2021-02-19 13:48 ` Eli Zaretskii
2021-02-19 14:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-20 4:35 ` Pip Cet
2021-02-20 8:56 ` Eli Zaretskii
2021-02-20 9:15 ` Pip Cet
2021-02-20 11:21 ` Eli Zaretskii
2021-02-20 11:48 ` Eli Zaretskii
2021-02-20 12:03 ` Pip Cet
2021-02-20 12:42 ` Eli Zaretskii
2021-02-20 17:00 ` Pip Cet
2021-02-20 17:18 ` Eli Zaretskii
2021-02-20 15:42 ` Stefan Monnier
2021-02-20 17:02 ` Pip Cet
2021-02-20 17:12 ` Stefan Monnier
[not found] ` <jwvo8etr7hf.fsf-monnier+emacs@gnu.org>
2021-04-05 2:56 ` Michael Welsh Duggan
2021-02-18 14:55 ` Michael Welsh Duggan
2021-02-18 15:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOqdjBf-NmpQjVxaX=HB+geNbDXd9EnwWzgenQMPqo78vsQFnQ@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=46502@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=mwd@md5i.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.