From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: cpuid 20211121
Date: Mon, 22 Nov 2021 03:19:08 -0700 [thread overview]
Message-ID: <20211122031908.9813-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following package has been upgraded in the Cygwin distribution:
* cpuid 20211121
The program displays detailed information about the CPU(s) gathered from
the CPUID instruction, and also determines the exact model of CPU(s).
Whereas /proc/cpuinfo is like an abstract of the features important to
Linux in a system, cpuid is a standalone utility which writes a paper
expounding on every feature in each CPU's architecture and what it can
do, at about the one line per bit level.
It is updated and released frequently and appears current with Intel and
AMD information and supports other vendors' chips.
See the project home page for more information:
http://etallen.com/cpuid.html
For information about changes since the previous Cygwin release,
see below or /usr/share/doc/cpuid/ChangeLog after installation.
Changes
* Removed __LARGE64_FILES from __CYGWIN__.
* Renamed macros with names starting with underscores, which are
reserved names in C: __THING -> MaskTHING, _THING -> ShftTHING.
* Added to (synth) decoding: AMD Ryzen 1000/2000/3000/4000/5000 series
numbers, Epyc Gen numbers.
* Distinguish (synth) decoding: AMD (8,15),(2,0) Dali CPUs: Ryzen vs.
other, Threadripper CPUs. For Zen & Zen+, only the brand
distinguishes; for Zen 2 (and rumored for Zen 3), there are distinct
models, Great Horned Owl & Banded Kestrel, Grey Hawk from Renoir.
* Added (synth) & (uarch synth) decoding for Intel (0,6),(11,14) Golden
Cove (Alder Lake) from Coreboot, (0,6),(6,7) Palm Cove (Cannon Lake),
(0,6),(10,11) Redwood Cove (Meteor Lake-N), (0,6),(11,10) Raptor Cove
(Raptor Lake-P) from DPTF.
* Added (synth) decoding for Intel (0,6),(11,7) Raptor Lake, from LX.
* Updated (uarch synth) phys strings for Intel 14nm and 10nm process
nodes using 14nm+, 14nm++, 14nm+++, 10nm+, 10nm++.
reply other threads:[~2021-11-22 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211122031908.9813-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/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.
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).