From: Guillaume Le Vaillant <glv@posteo.net>
To: Adam Kandur <rndd@tuta.io>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: problem with common lisp
Date: Sat, 24 Oct 2020 19:02:05 +0200 [thread overview]
Message-ID: <87a6wbk16a.fsf@yamatai> (raw)
In-Reply-To: <MKQUZiU--3-2@tuta.io>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Adam Kandur <rndd@tuta.io> skribis:
> Hi! thank you for this question. dont have to much knowledge about cpu. i attached lscpu output. if you find something interesting in it, let me know, please
>
> Oct 24, 2020, 16:35 by glv@posteo.net:
>
>>
>> Adam Kandur via <help-guix@gnu.org> skribis:
>>
>>> hi, i realized that i have this problem with sbcl itself, if i install sbcl in my main profile (without any of my packages, only sbcl from guix channel) i still got this error:
>>>
>>> fatal error encountered in SBCL pid 1954 tid 1954:
>>> Unhandled SIGILL at 0x52000e9d.
>>>
>>
>> Out of curiosity, what does the "lscpu" command return on your machine
>> (the flags in particular)?
>>
According to [1], there is a bug in SBCL 2.0.9 that causes an illegal
instruction error on CPUs that support the popcnt instruction but not
the AVX instructions. It it the case of your CPU.
This bug has been fixed in the master branch of SBCL's repository, so
the next version of SBCL (which will be released soon I think) should
work on your machine.
[1] https://www.reddit.com/r/sbcl/comments/j824cs/does_binary_209_require_some_fancy_x86/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-24 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 20:31 problem with common lisp Adam Kandur via
2020-10-21 21:44 ` zimoun
[not found] ` <MKC8lw5--3-2@tuta.io>
2020-10-21 22:51 ` zimoun
2020-10-24 15:59 ` Adam Kandur via
2020-10-24 16:35 ` Guillaume Le Vaillant
2020-10-24 16:43 ` Adam Kandur via
2020-10-24 17:02 ` Guillaume Le Vaillant [this message]
2020-10-22 8:27 ` Guillaume Le Vaillant
[not found] ` <MKFC0qb----2@tuta.io>
2020-10-22 12:28 ` Guillaume Le Vaillant
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=87a6wbk16a.fsf@yamatai \
--to=glv@posteo.net \
--cc=help-guix@gnu.org \
--cc=rndd@tuta.io \
/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.
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).