unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>, Andrea Corallo <akrl@sdf.org>
Cc: 63564@debbugs.gnu.org
Subject: bug#63564: 29.0.91; (setcdr) behaves differently between natively and byte compiled code
Date: Thu, 18 May 2023 09:50:21 +0300	[thread overview]
Message-ID: <83pm6yw2tu.fsf@gnu.org> (raw)
In-Reply-To: <m2jzx64b13.fsf@MobileCat.localdomain> (message from Jimmy Yuen Ho Wong on Thu, 18 May 2023 03:40:40 +0100)

> From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
> Date: Thu, 18 May 2023 03:40:40 +0100
> 
> 
> Users have discovered there's a markdown-mode function that behaves
> differently depending Emacs is executing byte-compiled code or natively
> compiled code.
> 
> The issue is documented
> [here](https://github.com/jrblevin/markdown-mode/issues/578).
> 
> 
> There are two examples in the issue that will produce an `Wrong type
> argument: consp, nil` error on the natively compiled version of
> `markdown-imenu-create-nested-index`, but not the byte-compiled or
> interpreted version.  A user has provided a disassembly of the natively
> compiled code for that function.
> 
> The last user has said and I can confirm the offending line seems to be `(setcdr
> sibling-alist alist)` in that function.
> 
> Much appreciate it if Andrea could take a look.

Adding Andrea.

While, of course, Andrea's help will be appreciated, there's currently
no reason to believe this is a problem in the Emacs core, and
therefore filing a bug report here could be premature.  Ideally, the
markdown-mode's developers should examine the problem first and
present convincing evidence that this is a problem with native
compilation and not with the code in markdown-mode itself.





  reply	other threads:[~2023-05-18  6:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  2:40 bug#63564: 29.0.91; (setcdr) behaves differently between natively and byte compiled code Jimmy Yuen Ho Wong
2023-05-18  6:50 ` Eli Zaretskii [this message]
2023-05-18  7:54   ` Andrea Corallo
2023-05-18 17:45     ` Jimmy Wong
2023-05-18 18:01       ` Mattias Engdegård
2023-05-18 18:58         ` Jimmy Wong
2023-05-18 18:25       ` Eli Zaretskii
2023-05-18  7:01 ` Mattias Engdegård

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=83pm6yw2tu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63564@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=wyuenho@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).