GNU bug report logs - #41574
gnu: Add xed.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: elaexuotee <at> wilsonb.com
Subject: bug#41574: closed (Re: [bug#41574] gnu: Add intel-xev.)
Date: Tue, 21 Jul 2020 21:04:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#41574: gnu: Add xed.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 41574 <at> debbugs.gnu.org.

-- 
41574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41574
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Marius Bakke <marius <at> gnu.org>
To: elaexuotee <at> wilsonb.com
Cc: 41574-done <at> debbugs.gnu.org
Subject: Re: [bug#41574] gnu: Add intel-xev.
Date: Tue, 21 Jul 2020 23:02:52 +0200

[Message part 3 (text/plain, inline)]

elaexuotee <at> 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!

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: elaexuotee <at> wilsonb.com
To: guix-patches <at> gnu.org
Subject: gnu: Add xed.
Date: Thu, 28 May 2020 17:41:52 +0900

[Message part 6 (text/plain, inline)]

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
   front.

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

[0001-gnu-Add-xed.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.