From: ppw0@tuta.io
To: Gcc <gcc@gcc.gnu.org>
Subject: Minor correction
Date: Sun, 2 Jul 2023 07:08:13 +0200 (CEST) [thread overview]
Message-ID: <NZK-4rA--3-9@tuta.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Hello there,
just wanted to let you know that while going over https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html , I've noticed certain sections, namely haswell, broadwell, skylake, knl, knm, skylake-avx512, cannonlake, icelake-client, icelake-server, cascadelake, cooperlake, tigerlake, sapphirerapids, rocketlake and graniterapids, have the MOVBE instruction mentioned twice.
Best Regards
next reply other threads:[~2023-07-02 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 5:08 ppw0 [this message]
2024-06-14 8:13 ` Gerald Pfeifer
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=NZK-4rA--3-9@tuta.io \
--to=ppw0@tuta.io \
--cc=gcc@gcc.gnu.org \
/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).