unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Daniel Kraus <daniel@kraus.my>
Cc: 41112@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#41112: 28.0.50; [feature/native-comp] Compiling treemacs-magit.el fails from the treemacs package
Date: Wed, 06 May 2020 22:08:38 +0000	[thread overview]
Message-ID: <xjf4kss1ztl.fsf@sdf.org> (raw)
In-Reply-To: <87tv0ttaek.fsf@kraus.my> (Daniel Kraus's message of "Wed, 06 May 2020 16:17:55 +0200")

Daniel Kraus <daniel@kraus.my> writes:

> Hi,
>
> I'm running the latest version of the native-comp branch (compiled yesterday, 2020-05-05) and
> while compiling the treemacs package (https://github.com/Alexander-Miller/treemacs/) I found out
> that `treemacs-magit.el` doesn't compile.
> The log output is:
>

Ok I managed to reproduce the and isolate the bug.

This is the funny sequence that goes out of limplification compiling an
expansion of the pcase in the expansion of treemacs--set-refresh-flags
inside treemacs-magit--simple-git-mode-update.

(cond-jump #s(comp-mvar 11631300 0 10 nil nil nil) #s(comp-mvar nil 0 nil t changed nil) bb_14 bb_14)
(jump bb_14)

The very interesing thing is that with all the code we have compiled
this the first bug in this pass since like December.

I'll fix it soon.

PS @Stefan is there a suggeted way to have the expantion of a
define-inline?  It would help in reducing for debugging this kind of
bugs.

--
akrl@sdf.org





  reply	other threads:[~2020-05-06 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:17 bug#41112: 28.0.50; [feature/native-comp] Compiling treemacs-magit.el fails from the treemacs package Daniel Kraus
2020-05-06 22:08 ` Andrea Corallo [this message]
2020-05-07 10:17   ` 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=xjf4kss1ztl.fsf@sdf.org \
    --to=akrl@sdf.org \
    --cc=41112@debbugs.gnu.org \
    --cc=daniel@kraus.my \
    --cc=monnier@iro.umontreal.ca \
    /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).