From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin-patches@cygwin.com
Subject: [PATCH] fhandler_proc.cc(format_proc_cpuinfo): fix bad bits in last change
Date: Tue, 15 Feb 2022 14:54:20 -0700 [thread overview]
Message-ID: <20220215215420.40254-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
move Linux 5.16 Gobble Gobble flags to 5.17 Superb Owl correct positions:
0x00000007:1 Intel Advanced Matrix eXtensions:
EAX:22 amx_bf16 Brain Float 16 dot product
EAX:24 amx_tile Tile matrix multiply
EAX:25 amx_int8 Int 8 byte dot product
0x00000007:0 Intel Advanced Matrix eXtensions:
EDX:22 amx_bf16 Brain Float 16 dot product
EDX:24 amx_tile Tile matrix multiply
EDX:25 amx_int8 Int 8 byte dot product
---
winsup/cygwin/fhandler_proc.cc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-fhandler_proc.cc-format_proc_cpuinfo-fix-bad-bits-in-last-change.patch --]
[-- Type: text/x-patch; name="0001-fhandler_proc.cc-format_proc_cpuinfo-fix-bad-bits-in-last-change.patch", Size: 1599 bytes --]
diff --git a/winsup/cygwin/fhandler_proc.cc b/winsup/cygwin/fhandler_proc.cc
index d51f171a3a41..0b01e68f8e50 100644
--- a/winsup/cygwin/fhandler_proc.cc
+++ b/winsup/cygwin/fhandler_proc.cc
@@ -1456,9 +1456,6 @@ format_proc_cpuinfo (void *, char *&destbuf)
ftcprint (features1, 4, "avx_vnni"); /* vex enc NN vec */
ftcprint (features1, 5, "avx512_bf16"); /* vec bfloat16 short */
- ftcprint (features1, 22, "amx_bf16"); /* Advanced Matrix eXtensions Brain Float 16 dot product */
- ftcprint (features1, 24, "amx_tile"); /* Advanced Matrix eXtensions Tile matrix multiply */
- ftcprint (features1, 25, "amx_int8"); /* Advanced Matrix eXtensions Int 8 byte dot product */
}
/* AMD cpuid 0x80000008 ebx */
@@ -1576,7 +1573,10 @@ format_proc_cpuinfo (void *, char *&destbuf)
ftcprint (features1, 16, "tsxldtrk"); /* TSX Susp Ld Addr Track */
ftcprint (features1, 18, "pconfig"); /* platform config */
ftcprint (features1, 19, "arch_lbr"); /* last branch records */
+ ftcprint (features1, 22, "amx_bf16"); /* Advanced Matrix eXtensions Brain Float 16 dot product */
ftcprint (features1, 23, "avx512_fp16"); /* avx512 fp16 */
+ ftcprint (features1, 24, "amx_tile"); /* Advanced Matrix eXtensions Tile matrix multiply */
+ ftcprint (features1, 25, "amx_int8"); /* Advanced Matrix eXtensions Int 8 byte dot product */
ftcprint (features1, 28, "flush_l1d"); /* flush l1d cache */
ftcprint (features1, 29, "arch_capabilities"); /* arch cap MSR */
}
next reply other threads:[~2022-02-15 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 21:54 Brian Inglis [this message]
2022-02-16 8:32 ` Corinna Vinschen
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=20220215215420.40254-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@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).