From: zimoun <zimon.toutoune@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Konrad Hinsen <konrad.hinsen@fastmail.net>,
"Thompson, David" <dthompson2@worcester.edu>
Cc: 57878@debbugs.gnu.org
Subject: bug#57878: Minimal reproducible setup
Date: Sat, 15 Oct 2022 17:40:50 +0200 [thread overview]
Message-ID: <86o7ud9jst.fsf@gmail.com> (raw)
In-Reply-To: <2ef3c47fabb502a231a028c790aeeed10bdc5511.camel@gmail.com>
Hi Liliana,
On Sat, 15 Oct 2022 at 16:40, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> Done. Since I just copypasta'd the wording, I made you the author.
Oh, thanks. (It was the news’ wording. :-))
> As for this bug: I've bumped emacs-next to a version that can inhibit
> almost all native-compilation (trampolines are still compiled, but not
> written to the cache), fixed the linker issue, and disabled native
> compilation for emacs-ido-completing-read+. Any remaining native-comp
> issues or can this be closed?
Closing is fine with me; well I do not have a opinion on that. :-)
Just to be sure, do you mean an emacs-next version which includes the
upstream Lars’s patches? The ones that Eli and Andrea are calling to be
reverted?
--8<---------------cut here---------------start------------->8---
Sorry as changeset I meant 5fec9182db + f97993ee66. I'm not against
e245c4f226.
[...]
Again 5fec9182db + f97993ee66 are IMO not useful / wrong, they were not
discussed and are just a step backward. The best change I can suggest
is to revert them now.
--8<---------------cut here---------------end--------------->8---
from <https://yhetil.org/emacs-devel/xjfk05e5k9t.fsf@ma.sdf.org/>
Cheers,
simon
next prev parent reply other threads:[~2022-10-15 15:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 9:09 bug#57878: Emacs native compilation on startup can crash the system Konrad Hinsen
2022-09-17 10:28 ` bug#57878: Minimal reproducible setup Konrad Hinsen
2022-09-17 15:45 ` Konrad Hinsen
2022-09-17 23:19 ` Liliana Marie Prikler
2022-09-18 18:35 ` Liliana Marie Prikler
2022-09-19 6:04 ` Konrad Hinsen
2022-09-19 8:51 ` Konrad Hinsen
2022-10-02 0:15 ` Thompson, David
2022-10-02 0:23 ` Liliana Marie Prikler
2022-10-02 8:25 ` Konrad Hinsen
2022-10-12 19:42 ` Liliana Marie Prikler
2022-10-13 9:31 ` Max Brieiev
2022-10-13 18:23 ` Liliana Marie Prikler
2022-10-14 16:07 ` zimoun
2022-10-14 18:22 ` Liliana Marie Prikler
2022-10-15 10:11 ` zimoun
2022-10-15 14:40 ` Liliana Marie Prikler
2022-10-15 15:40 ` zimoun [this message]
2022-10-15 16:30 ` Liliana Marie Prikler
2022-10-25 16:23 ` Max Brieiev
2022-10-25 18:31 ` Liliana Marie Prikler
2022-10-26 7:46 ` zimoun
2022-10-11 10:04 ` zimoun
2022-10-13 10:06 ` Max Brieiev
2023-10-12 14:50 ` bug#57878: Emacs native compilation on startup can crash the system Ludovic Courtès
2023-10-14 14:37 ` Konrad Hinsen
2022-12-09 14:30 ` bug#57878: Some further investigation Konrad Hinsen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86o7ud9jst.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=57878@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
--cc=konrad.hinsen@fastmail.net \
--cc=liliana.prikler@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/guix.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).