GNU bug report logs - #63288
30.0.50; Emacs 30 packages fail to build with native comp on some machines

Previous Next

Full log

View this message in rfc822 format

From: Pip Cet <pipcet <at> protonmail.com>
To: "Basil L. Contovounesios" <basil <at> contovou.net>
Cc: damien <at> merenne.me, Eli Zaretskii <eliz <at> gnu.org>, acorallo <at> gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>, 63288 <at> debbugs.gnu.org
Subject: bug#63288: 30.0.50; Emacs 30 packages fail to build with native comp on some machines
Date: Wed, 19 Feb 2025 20:06:31 +0000

"Basil L. Contovounesios" <basil <at> contovou.net> writes:

> Pip Cet [2025-02-17 15:16 +0000] wrote:
>
>> "Stefan Monnier" <monnier <at> iro.umontreal.ca> writes:
>>
>>> For the case at hand, I think a better option is to add keyword
>>> arguments to `cl-defstruct` to control whether accessors need to check
>>> the type of their arg.
>
> +1.
>
>> That makes sense to me. Setting byte-compile-delete-errors means you
>> cannot compile any "normal" Elisp code, not just skipped type checks.
>> It's -Ofast, not -DNDEBUG; you should never use the former, only the
>> latter.
>
> Does setting byte-compile-delete-errors actually have the same effect?
> I couldn't get it to behave like (cl-declaim (optimize (safety 0)))
> for cl-defstruct accessors.

I'm not sure I understand.  byte-compile-delete-errors will cause the
compilation errors described, but I don't think it would change the code
generated by cl-defstruct....

Pip

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.