From: Eli Zaretskii <eliz@gnu.org>
To: Al Haji-Ali <abdo.haji.ali@gmail.com>, Andrea Corallo <akrl@sdf.org>
Cc: 61917@debbugs.gnu.org
Subject: bug#61917: 29.0.60; native compilation issues
Date: Thu, 02 Mar 2023 17:48:52 +0200 [thread overview]
Message-ID: <83wn3zcfx7.fsf@gnu.org> (raw)
In-Reply-To: <87zg8vmbb4.fsf@gmail.com> (message from Al Haji-Ali on Thu, 02 Mar 2023 15:18:23 +0000)
> From: Al Haji-Ali <abdo.haji.ali@gmail.com>
> 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)
Adding Andrea.
next prev parent reply other threads:[~2023-03-02 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:18 bug#61917: 29.0.60; native compilation issues Al Haji-Ali
2023-03-02 15:48 ` Eli Zaretskii [this message]
[not found] ` <xjfzg8uxi7b.fsf@ma.sdf.org>
2023-03-09 10:08 ` Eli Zaretskii
2023-03-09 11:33 ` Andrea Corallo
2023-03-09 12:20 ` Eli Zaretskii
2023-03-09 16:35 ` Al Haji-Ali
2023-03-10 16:55 ` Andrea Corallo
[not found] ` <xjf4jqfqoy0.fsf@ma.sdf.org>
2023-03-23 15:43 ` Al Haji-Ali
2023-03-25 12:49 ` Naofumi Yasufuku
2023-03-25 14:46 ` Andrea Corallo
2023-03-25 19:55 ` Naofumi Yasufuku
2023-03-26 8:22 ` Andrea Corallo
2023-03-26 9:20 ` Andrea Corallo
2023-03-29 20:29 ` Andrea Corallo
2023-03-29 22:53 ` Naofumi Yasufuku
2023-03-30 13:14 ` Naofumi Yasufuku
2023-03-30 13:32 ` Andrea Corallo
2023-04-09 17:48 ` Dmitry Gutov
2023-03-10 16:54 ` Andrea Corallo
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=83wn3zcfx7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61917@debbugs.gnu.org \
--cc=abdo.haji.ali@gmail.com \
--cc=akrl@sdf.org \
/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).