From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: leungbk@posteo.net, mattias.engdegard@gmail.com, 63674@debbugs.gnu.org
Subject: bug#63674: 30.0.50; Possible miscompilation of cl-structs?
Date: Sun, 28 May 2023 08:31:48 +0000 [thread overview]
Message-ID: <xjfcz2kyhzf.fsf@ma.sdf.org> (raw)
In-Reply-To: <83a5xqjmym.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 May 2023 09:41:05 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: Brian Leung <leungbk@posteo.net>, 63674@debbugs.gnu.org
>> From: Andrea Corallo <akrl@sdf.org>
>> Date: Wed, 24 May 2023 13:18:34 +0000
>>
>> Mattias Engdegård <mattias.engdegard@gmail.com> writes:
>>
>> >> After the latest changes to native compilation, I see a failure here:
>> >> https://github.com/nix-community/emacs-overlay/actions/runs/5059662673/jobs/9081521991#step:6:7010.
>> >
>> > CC:ing Andrea.
>>
>> Thanks, will look at as soon as I can.
>>
>> PS I merged 63679 63679 63681 as I believe are the same.
>
> Your merge didn't succeed, it seems.
That's strange I think I got the message confirming that.
> And people are still complaining about problems with package.el that
> seem to be related to native compilation. So could you please look
> into those other issues (bug#63742, bug#63710)?
Sure, I did already some work on that and today is dedicated to this
bug.
BR
Andrea
next prev parent reply other threads:[~2023-05-28 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 3:48 bug#63674: 30.0.50; Possible miscompilation of cl-structs? Brian Leung
2023-05-24 10:09 ` Mattias Engdegård
2023-05-24 10:39 ` Brian Leung
2023-05-25 0:09 ` Brian Leung
2023-05-24 13:18 ` Andrea Corallo
2023-05-24 15:27 ` Andrea Corallo
2023-05-27 6:41 ` Eli Zaretskii
2023-05-28 8:31 ` Andrea Corallo [this message]
2023-05-28 10:42 ` Andrea Corallo
2023-05-28 12:39 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfcz2kyhzf.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=63674@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=leungbk@posteo.net \
--cc=mattias.engdegard@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.