GNU bug report logs - #61917
29.0.60; native compilation issues

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Al Haji-Ali <abdo.haji.ali <at> gmail.com>
Subject: bug#61917: closed (Re: bug#61917: 29.0.60; native compilation issues)
Date: Thu, 30 Mar 2023 13:33:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#61917: 29.0.60; native compilation issues

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 61917 <at> debbugs.gnu.org.

-- 
61917: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61917
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andrea Corallo <akrl <at> sdf.org>
To: Naofumi Yasufuku <naofumi <at> yasufuku.dev>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Al Haji-Ali <abdo.haji.ali <at> gmail.com>,
 61917-done <at> debbugs.gnu.org
Subject: Re: bug#61917: 29.0.60; native compilation issues
Date: Thu, 30 Mar 2023 13:32:25 +0000

Naofumi Yasufuku <naofumi <at> yasufuku.dev> writes:

> Naofumi Yasufuku <naofumi <at> yasufuku.dev> writes:
>
>> Andrea Corallo <akrl <at> sdf.org> writes:
>>
> [..snip..]
>>>
>>> Okay ab4273056e0 should be a better (and safer) fix for this bug, I
>>> pushed it now to 29.  This time hopefully it does not cause
>>> regressions...
>>>
>>> Bests
>>>
>>>   Andrea
>>
>> Thank you.  I will try ;-)
>>
>
> Hi Andrea,
>
> I've confirmed that my build of emacs-29 ab4273056e0 works well.
> Thank you very much for your great work.
>
> - Recompiled all .elc and .eln successfully.
>
> - .eln issues of both yasnippet and ddskk (Japanese input method) have gone.
>   They are successfully loaded, and work without any problem.

Wonderful, thank you very much for reporting!

Closing this then.

Bests

  Andrea

[Message part 3 (message/rfc822, inline)]

From: Al Haji-Ali <abdo.haji.ali <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.0.60; native compilation issues
Date: Thu, 02 Mar 2023 15:18:23 +0000

I've ran into a few issues with native compilation that I would like to report here in case they are unintentional bugs.

- First, native-compiling a simple file like

(defun test ()
  '(A . B))

after setting a non-zero native-comp-verbose, for example by running:

(let ((native-comp-verbose 1))
    (native-compile buffer-file-name))

gives the error `wrong-type-argument (listp B)`
in `comp-prettyformat-insn`

- Another issue I noticed is that if a file has `no-native-compile: t` and I call `emacs-lisp-native-compile-and-load` anyways on it, I get an error: `Wrong type argument: stringp, nil`. Not sure if this is intended.

- I've also had the following error when compiling a large file with many components (if more information is needed, I can try to pinpoint the reason once verbose debugging is fixed as it is making debugging difficult)

libgccjit.so: error: gcc_jit_context_new_call_through_ptr: mismatching types for argument 1 of fn_ptr: freloc->R64656c6574652d726567696f6e_delete_region_0: assignment to param 1 (type: struct Lisp_X *) from (long long)2 (type: long long)


Best regards,
-- Al

Previous Next

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