From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 61586@debbugs.gnu.org
Subject: [bug#61586] [PATCH RFC 0/2] Add BinaryEn
Date: Fri, 17 Feb 2023 21:45:33 +0100 [thread overview]
Message-ID: <2cc4a1091e54c0fec082de4ce2789dfc42470e54.camel@gmail.com> (raw)
Hi Guix,
this series gets us a little closer to having a "full" WebAssembly stack.
It packages binaryen, on top of which other compilers such as emscripten
or AssemblyScript (a sort of Typescript?) are built.
However, there is a grain of salt. It appears binaryen has some rather
esoteric use for -msse2 on i686: Rather than performance, it wants it
for precision. Needless to say, this would break compatibility with
older CPUs. I'm wondering if we should simply drop i686 (and similarly
32-bit ARM) from supported-systems or whether there's a more clever
hack to use here.
Cheers
Liliana Marie Prikler (2):
gnu: Add python-filecheck.
gnu: Add binaryen.
gnu/packages/check.scm | 25 +++++++++++++++++++++++
gnu/packages/web.scm | 45 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 70 insertions(+)
base-commit: 312f1f41d3f3f3e5d2c36ff46920c6dce1c21a17
--
2.39.1
next reply other threads:[~2023-02-17 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:45 Liliana Marie Prikler [this message]
2023-02-17 20:27 ` [bug#61586] [PATCH RFC 1/2] gnu: Add python-filecheck Liliana Marie Prikler
2023-02-17 20:28 ` [bug#61586] [PATCH RFC 2/2] gnu: Add binaryen Liliana Marie Prikler
2023-04-06 21:38 ` Thompson, David
2023-06-11 8:04 ` bug#61586: " Liliana Marie Prikler
2023-03-11 22:48 ` [bug#61586] BinaryEn Andreas Enge
2023-03-12 8:16 ` Liliana Marie Prikler
2023-03-12 10:49 ` Andreas Enge
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=2cc4a1091e54c0fec082de4ce2789dfc42470e54.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=61586@debbugs.gnu.org \
/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.