From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Tai <atai@atai.org>
Cc: 63888-done@debbugs.gnu.org
Subject: bug#63888: [PATCH] gnu: Add neon2sse
Date: Sat, 01 Jul 2023 18:05:55 +0200 [thread overview]
Message-ID: <87pm5by5uk.fsf_-_@gnu.org> (raw)
In-Reply-To: <2f8bd93b222ad34c8a8a27f0f2624e0292164fe9.1685917952.git.atai@atai.org> (Andy Tai's message of "Sun, 4 Jun 2023 15:33:17 -0700")
[-- Attachment #1: Type: text/plain, Size: 153 bytes --]
Andy Tai <atai@atai.org> skribis:
> * gnu/packages/assembly.scm (neon2sse): New variable
Hi! Applied with the edits below.
Thanks,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1027 bytes --]
diff --git a/gnu/packages/assembly.scm b/gnu/packages/assembly.scm
index 30b0b27482..104e61f63f 100644
--- a/gnu/packages/assembly.scm
+++ b/gnu/packages/assembly.scm
@@ -576,10 +576,11 @@ (define-public neon2sse
(home-page "https://github.com/intel/ARM_NEON_2_x86_SSE")
(synopsis "Header file to simplify ARM->IA32 porting")
(description
- "The NEON_2_SSE.h file is intended to simplify ARM->IA32 porting. It makes
-the correspondence (or a real porting) of ARM NEON intrinsics as defined in
-arm_neon.h header and x86 SSE (up to SSE4.2) intrinsic functions as defined
-in corresponding x86 compilers headers files.")
- (license license:expat))))
+ "The @file{NEON_2_SSE.h} file is intended to simplify ARM-to-IA32
+porting. It makes the correspondence (or a real porting) of ARM NEON
+intrinsics as defined in the @file{arm_neon.h} header and x86 SSE (up to
+SSE4.2) intrinsic functions as defined in corresponding x86 compilers headers
+files.")
+ (license license:bsd-2))))
prev parent reply other threads:[~2023-07-01 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 8:26 [bug#63888] [PATCH] gnu: Add neon2sse Andy Tai
2023-06-04 22:33 ` [bug#63888] [PATCH v2] " Andy Tai
2023-07-01 16:05 ` Ludovic Courtès [this message]
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=87pm5by5uk.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=63888-done@debbugs.gnu.org \
--cc=atai@atai.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 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).