GNU bug report logs - #46495
28.0.50; [native-comp] Build fails for 32bit --with-wide-int

Previous Next

Package: emacs;

Reported by: Andy Moreton <andrewjmoreton <at> gmail.com>

Date: Sat, 13 Feb 2021 17:58:02 UTC

Severity: normal

Found in version 28.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Forwarded to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99126

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: akrl <at> sdf.org
Cc: andrewjmoreton <at> gmail.com, dmalcolm <at> redhat.com, 46495 <at> debbugs.gnu.org
Subject: Re: bug#46495: 28.0.50;
 [native-comp] Build fails for 32bit --with-wide-int
Date: Wed, 31 Mar 2021 13:19:16 +0300
> Date: Wed, 31 Mar 2021 13:01:36 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: andrewjmoreton <at> gmail.com, dmalcolm <at> redhat.com, 46495 <at> debbugs.gnu.org
> 
> For some reason, compiling files with batch-native-compile does NOT
> produce the message that I'm used to see with
> batch-byte-native-compile-for-bootstrap:
> 
>   libgccjit-0.dll: note: disable pass tree-isolate-paths for functions in the range of [0, 4294967295]

Oh, I see: it's because batch-native-compile runs the final
compilation phase in a subprocess.  But doesn't that mean the
non-default setting of comp-debug will not have its effect in this
case?

Btw, I find the doc strings of the various top-level native-compile
functions not very helpful when I need to understand under what
circumstances they run the compilation asynchronously.  I always need
to read the code, and read it carefully, to figure that out.  Can this
please be improved?




This bug report was last modified 4 years and 43 days ago.

Previous Next


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