From: Efraim Flashner <efraim@flashner.co.il>
To: Eric Bavier <bavier@posteo.net>
Cc: andreas@enge.fr, sharlatanus@gmail.com, 73200@debbugs.gnu.org
Subject: [bug#73200] [PATCH] gnu: sleef: Update to 3.6.1.
Date: Sun, 15 Sep 2024 15:48:07 +0300 [thread overview]
Message-ID: <ZubXh_fmw-RAo90I@3900XT> (raw)
In-Reply-To: <8244F0B2-F933-4703-8619-9EEF8374CA19@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
On Fri, Sep 13, 2024 at 02:11:09PM +0000, Eric Bavier wrote:
> Hi Efraim,
>
> Also looks good to me. I tested with build of llama-cpp for x86_64. Some other Python users currently FTBFS for other reasons it seems.
>
> This version of Sleef even comes with RISC-V Vector extension support :-) .
>
> `~Eric
I think for the vector support on RISC-V we need to build with gcc-14 or
llvm-17+.
At first build this fixes build failures on aarch64 and riscv64, but
breaks support for i686 and one of the other architectures. I was hoping
to get feedback from the QA system to see if it built there and just not
on my hardware.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-15 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 15:29 [bug#73200] [PATCH] gnu: sleef: Update to 3.6.1 Efraim Flashner
2024-09-13 9:18 ` Andreas Enge
2024-09-15 12:47 ` Efraim Flashner
2024-09-16 9:35 ` Andreas Enge
2024-09-13 14:11 ` Eric Bavier
2024-09-15 12:48 ` Efraim Flashner [this message]
[not found] ` <handler.73200.B.172615500332605.ack@debbugs.gnu.org>
2024-09-17 18:25 ` bug#73200: Acknowledgement ([PATCH] gnu: sleef: Update to 3.6.1.) Efraim Flashner
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=ZubXh_fmw-RAo90I@3900XT \
--to=efraim@flashner.co.il \
--cc=73200@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=bavier@posteo.net \
--cc=sharlatanus@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/guix.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.