[Bug 265368] [New Port] benchmarks/uica: uops.info Code Analyzer

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 21 Jul 2022 22:10:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265368

            Bug ID: 265368
           Summary: [New Port] benchmarks/uica: uops.info Code Analyzer
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: fuz@fuz.su
                CC: python@FreeBSD.org
 Attachment #235413 maintainer-approval+
             Flags:

Created attachment 235413
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235413&action=edit
[New Port] benchmarks/uica: uops.info Code Analyzer

uiCA is a simulator that can predict the throughput of basic blocks on
recent Intel microarchitectures. In addition to that, it also provides
insights into how the code is executed.

uiCA is based on data from uops.info, combined with a detailed pipeline
model. Like related tools, it assumes that all memory accesses result in
cache hits.

WWW: https://uops.info/uiCA.html

Tested with Poudriere on armv7 arm64 i386 amd64 FreeBSD 13.1.
Portclippy likes the port.
Portlint has two issues:

 - it doesn't like the PORTVERSION, I think that's a bug (cf. bug #265364)
 - it doesn't like COMMENT= uops.info Code Analyzer

For the latter, the comment could be changed if needed, but as is, it's pretty
much exactly what the software is.  uops.info is a domain name and should be
rendered in lower case letters.  Perhaps an exception to the guidelines can be
made here.

On another note, this port is a Python port and doesn't come with distutils or
the like.  I have tried to get the packaging right, but alas I'm not a Python
expert and may have made some sort of terrible mistake.  Please may someone
with more experience check this one.

The special treatment of the xml distfile is due to upstream naming the most
recent version "instructions.xml".  When a new version comes out, the current
version is moved to a dated file name.  I try to work around this by trying
both, banking on distinfo to reject the undated file if it has changed.

-- 
You are receiving this mail because:
You are the assignee for the bug.