[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#41574: closed (gnu: Add xed.)

From: GNU bug Tracking System
Subject: bug#41574: closed (gnu: Add xed.)
Date: Tue, 21 Jul 2020 21:04:02 +0000

Your message dated Tue, 21 Jul 2020 23:02:52 +0200
with message-id <87r1t4fuo3.fsf@gnu.org>
and subject line Re: [bug#41574] gnu: Add intel-xev.
has caused the debbugs.gnu.org bug report #41574,
regarding gnu: Add xed.
to be marked as done.

(If you believe you have received this mail in error, please contact

41574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41574
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: gnu: Add xed. Date: Thu, 28 May 2020 17:41:52 +0900 User-agent: mblaze/0.7
This patch packages up Intel's X86 Encoder and Decoder library and associated
cli tool "examples."

A few things of note:

1) The build uses Intel's custom Python build tool `mbuild' so we have to
   manually handle the main build phases. We may need to add explicit options
   to the build script invocation so that build variables (e.g. CFLAGS etc.)
   propogate correctly. These don't look to be set in the environment, so what
   variables should we pick be picking up and from where?

2) The group of tests under `tests/tests-avx512pf' seems to be failing. A user
   on the irc channel also cross-checked for me and confirmed the same. This
   program isn't actually *executing* the avx instructions, so I don't think
   the failing test are specific to the executing cpu. Anyway, I opted to leave
   this test in the source commented out.

3) The commands provided by the `out' output are pretty poorly documented and
   have dumb names. I suspose this is becase the utilities are branded as just
   "examples" of using the library. Anyway, this is a case where the only
   reasonable documentation is the source code, so I provide that for the
   utilities in the `doc' output.

4) Finally, the `devel' output supplies the library and headers proper.

5) The package name `xed' potentially collides with the package from
   http://xed.sourceforge.net/. We don't currently have the latter yet, but I
   mention this just in case there is a good way to proactively handle this up

Thoughts? I threw this together just because I wanted it myself but figured
it's worth sharing.

Attachment: 0001-gnu-Add-xed.patch
Description: Text Data

Attachment: signature.asc
Description: PGP signature

--- End Message ---
--- Begin Message --- Subject: Re: [bug#41574] gnu: Add intel-xev. Date: Tue, 21 Jul 2020 23:02:52 +0200
elaexuotee@wilsonb.com writes:

>> Apart from these minor issues, I think it's good to go.  \o/
>> Can you send an updated patch?  TIA!  :-)
> Here you go!

Sorry for the delay, this patch got lost in my horrifying email queue.

Applied now!

Attachment: signature.asc
Description: PGP signature

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]