public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin cpuid Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: cpuid 20230614
Date: Sat, 17 Jun 2023 13:04:53 -0600	[thread overview]
Message-ID: <20230617130453.27965-1-Brian.Inglis@Shaw.ca> (raw)

The following package has been upgraded in the Cygwin distribution:

* cpuid		20230614

Displays detailed information about the CPU(s) gathered from the
CPUID instruction, and also determines the exact model of CPU(s).
Where /proc/cpuinfo shows features important to a system, cpuid shows
what every feature in each CPU's architecture does.
It is updated and released frequently to stay 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.


Wed Jun 14 2023		20230614

cpuid.c:

- Improved (synth) identification for (0,6),(5,5),10 Intel Xeon Scalable
  (3rd Gen) (Cooper Lake A0), based on 634897 doc.
- Changed (synth) identification for (0,6),(6,12) Intel Xeon D-1700/2700
  (Ice Lake-D). Intel docs 714071 claim the stepping is U1/U2, which
  contradicts ILPMDF*. I'm using the actual docs.
- Updated comments with new Intel docs.
- Changed "Intel Scalable" to "Intel Xeon Scalable".
- Added (synth) differentiation for (0,6),(9,10),4 Intel Pentium Gold
  8500 series.
- Made the (simple synth) fields non-default. Too many people were
  interpreting them as definitive and ignoring the much better (synth)
  leaf, which uses the entirety of cpuid information. This impacts
  leaves 1, 0x80000001, and 0x80860001.  The (simple synth) fields still
  are available, but only with the -S/--simple option.
- Organized option flags that need to be passed deeply down in the
  print_reg* functions into a new print_opts_t, which will make future
  options easier to add.
- Renamed the old "try" variables to "sub". The word "try" was a remnant
  of the original leaf 4 subleaf implemntation, before subleaves were
  commonplace. For leaf 4, one just kept "trying" to read more cache
  data until it failed. But most subleaves don't work that way.
- Updated (synth) decoding for (0,6),(8,15),{7,8} to mention steppings
  {S2,S3} from ILPMDF* 20230512.
- Added (synth) decoding for (0,6),(11,14) pure Atom x7000E, as a
  variation on other Alder Lake-N CPUs.
- Added (synth) decoding for (0,6),(9,10),4 Atom C1100 Arizona Beach.

cpuid.man:

- Added new Intel docs.
- Added 613537, the new pub number for 336065, Intel Xeon Processor
  Scalable Family Specification Update.


                 reply	other threads:[~2023-06-17 19:06 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=20230617130453.27965-1-Brian.Inglis@Shaw.ca \
    --to=brian.inglis@shaw.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).