From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: Michael Welsh Duggan <mwd@md5i.com>, 46502@debbugs.gnu.org
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Thu, 18 Feb 2021 10:29:41 +0000 [thread overview]
Message-ID: <xjfczwxpt2i.fsf@sdf.org> (raw)
In-Reply-To: <CAOqdjBfzAaxDasgjU4EHyb2qvhhcHga6A=D7861yfuVUeXgOWw@mail.gmail.com> (Pip Cet's message of "Thu, 18 Feb 2021 10:14:24 +0000")
Pip Cet <pipcet@gmail.com> writes:
> On Thu, Feb 18, 2021 at 10:04 AM Andrea Corallo via Bug reports for
> GNU Emacs, the Swiss army knife of text editors
> <bug-gnu-emacs@gnu.org> wrote:
>> Michael Welsh Duggan <mwd@md5i.com> writes:
>> > I decided to attempt building the native-comp feature branch, since it
>> > seems like it may make it to mainline fairly soon. When bootstrapping
>> > with
>> >
>> > make NATIVE_FULL_AOT=1 -j 32 bootstrap
>> >
>> > I get an error compiling gnus/gnus-icalendar.el. I've put the log
>> > below. I've updated the emacs information from my running emacs below
>> > to match the version of the repository from which I built.
>> >
>> >
>> > In GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0)
>> > of 2021-02-13 built on miko
>> > Repository revision: d3a399dd299bf7e811cf42950d5f8ac67f063b36
>> > Repository branch: native-comp
>> > Windowing system distributor 'The X.Org Foundation', version 11.0.12010000
>> > System Description: Debian GNU/Linux bullseye/sid
>> >
>> > Configured using:
>> > 'configure --without-toolkit-scroll-bars --with-x-toolkit=lucid --with-nativecomp'
>> >
>> >
>> > Debugger entered--Lisp error: (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
>>
>> Hi Michael,
>>
>> just tried compiling the current branch (f92bb788a0) following your
>> configuration with no issues. Could you retry on the current head maybe
>> starting from a "git clean -xfd" to be on the safe side?
>
> 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.
>
> We should fix that, and it might lead to the behavior Michael has
> observed (macroexp being executed from source code when compiling
> gnus)...
>
> BTW, I'm also seeing very deep recursion when building the nativecomp
> branch, even outside of the garbage collector (which is easy to "fix"
> so it allocates more than one object at the same time on the C stack).
> Maybe we can avoid that by doing an -O0 compile first, then compiling
> the optimized compiler with the unoptimized one?
Agree, I think might be even better in terms of bootstrap time to just
byte compile the initial COMPILE_FIRST files and then re-compiling and
loading them nativelly later-on (before dumping).
Never had time to tackle this.
Andrea
next prev parent reply other threads:[~2021-02-18 10:29 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 [this message]
2021-02-18 14:34 ` Eli Zaretskii
2021-02-19 13:31 ` Pip Cet
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
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=xjfczwxpt2i.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=46502@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=mwd@md5i.com \
--cc=pipcet@gmail.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 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).