From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: andrewjmoreton@gmail.com, dmalcolm@redhat.com, 46495@debbugs.gnu.org
Subject: bug#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int
Date: Wed, 31 Mar 2021 11:07:20 +0300 [thread overview]
Message-ID: <83o8eziw5j.fsf@gnu.org> (raw)
In-Reply-To: <xjflfa4o3f3.fsf@sdf.org> (message from Andrea Corallo on Tue, 30 Mar 2021 19:19:12 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: dmalcolm@redhat.com, andrewjmoreton@gmail.com, 46495@debbugs.gnu.org
> Date: Tue, 30 Mar 2021 19:19:12 +0000
>
> >> `batch-native-compile' or `batch-byte-native-compile-for-bootstrap'
> >> should be equivalent here as the second is just a way to do only byte
> >> compilation for non dumped files when we are not using NATIVE_FULL_AOT.
> >
> > Then I guess I'm missing something: how does Emacs know whether a
> > given .eln file should be saved in native-lisp/ or in
> > ~/.emacs.d/eln-cache/?
>
> Ops apologies you are correct, `batch-byte-native-compile-for-bootstrap'
> also select as destination folder the `native-lisp' directory in the
> build tree. It is correct to invoke
> `batch-byte-native-compile-for-bootstrap' if we want the .eln to be
> deposed there.
OK, thanks.
Another nit: the doc string of comp-debug says:
0 no debugging output.
This is the recommended value unless you are debugging the compiler itself.
1 emit debug symbols and dump pseudo C code.
2 dump gcc passes and libgccjit log file.
3 dump libgccjit reproducers.
But comp.c does this:
if (comp.debug)
gcc_jit_context_set_bool_option (comp.ctxt,
GCC_JIT_BOOL_OPTION_DEBUGINFO,
1);
if (comp.debug > 2)
{
logfile = emacs_fopen ("libgccjit.log", "w");
gcc_jit_context_set_logfile (comp.ctxt,
logfile,
0, 0);
gcc_jit_context_set_bool_option (comp.ctxt,
GCC_JIT_BOOL_OPTION_KEEP_INTERMEDIATES,
1);
gcc_jit_context_set_bool_option (comp.ctxt,
GCC_JIT_BOOL_OPTION_DUMP_EVERYTHING,
1);
}
[...]
if (comp.debug)
gcc_jit_context_dump_to_file (comp.ctxt,
format_string ("%s.c", SSDATA (ebase_name)),
1);
AFAIU, this means the libgccjit log file is only output with
comp-debug 3 and higher? Also, does comp-debug = 3 indeed cause the
reproducer to be written, or is that controlled independently by
comp-libgccjit-reproducer?
And finally, what do you think about moving the
gcc_jit_context_dump_to_file call to comp-debug 2 or higher? IOW,
make level 1 just add debug info to the *.eln files? Especially if we
are going to make comp-debug = 1 the default (as I think we should),
wouldn't it be better than the current setup? Or maybe we should
introduce an intermediate debug level between the current 0 and 1?
And if we make that change, do we also need to bump the ABI number?
Thanks.
next prev parent reply other threads:[~2021-03-31 8:07 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 17:57 bug#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int Andy Moreton
2021-02-13 18:10 ` Eli Zaretskii
2021-02-13 20:23 ` Andy Moreton
2021-02-14 15:59 ` Eli Zaretskii
2021-02-14 13:24 ` Andy Moreton
2021-02-14 15:56 ` Eli Zaretskii
2021-02-14 19:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-15 9:01 ` Andy Moreton
2021-02-15 10:19 ` Eli Zaretskii
2021-02-15 12:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 9:34 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 15:29 ` Eli Zaretskii
2021-02-16 16:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 17:01 ` Eli Zaretskii
2021-02-16 17:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 19:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 21:51 ` Andy Moreton
2021-02-17 9:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-17 18:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 22:36 ` Andy Moreton
2021-02-19 14:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-19 16:01 ` Andy Moreton
2021-02-19 16:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-19 17:01 ` Eli Zaretskii
2021-02-19 17:35 ` Andy Moreton
2021-02-19 19:36 ` Eli Zaretskii
2021-02-19 22:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-26 10:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-26 11:27 ` Eli Zaretskii
2021-03-26 13:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-29 15:55 ` Eli Zaretskii
2021-03-29 16:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-29 16:59 ` Eli Zaretskii
2021-03-29 18:11 ` David Malcolm
2021-03-29 20:46 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-30 7:50 ` Eli Zaretskii
2021-03-30 9:06 ` Eli Zaretskii
2021-03-31 8:13 ` Eli Zaretskii
2021-03-31 13:03 ` David Malcolm
2021-03-31 13:13 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 13:35 ` Eli Zaretskii
2021-03-31 13:33 ` Eli Zaretskii
2021-03-30 9:22 ` Eli Zaretskii
2021-03-30 14:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-30 14:37 ` Eli Zaretskii
2021-03-30 19:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 8:07 ` Eli Zaretskii [this message]
2021-03-31 8:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 11:41 ` Eli Zaretskii
2021-03-31 12:16 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:27 ` Eli Zaretskii
2021-03-31 18:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:01 ` Eli Zaretskii
2021-03-31 10:19 ` Eli Zaretskii
2021-03-31 10:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:55 ` Eli Zaretskii
2021-03-31 12:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:41 ` Eli Zaretskii
2021-03-31 12:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 11:10 ` Eli Zaretskii
2021-03-31 12:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:33 ` Eli Zaretskii
2021-03-31 18:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 19:16 ` Eli Zaretskii
2021-03-31 19:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 19:35 ` Eli Zaretskii
2021-03-31 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 6:37 ` Eli Zaretskii
2021-04-01 7:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 7:42 ` Eli Zaretskii
2021-04-01 8:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 8:43 ` Eli Zaretskii
2021-04-01 14:16 ` Michael Welsh Duggan
2021-04-01 19:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 16:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 17:38 ` Eli Zaretskii
2021-03-31 19:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:24 ` 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=83o8eziw5j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46495@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=andrewjmoreton@gmail.com \
--cc=dmalcolm@redhat.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).