public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pc-gcc22 at crowcastle dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104683] -march=haswell generates invalid instructions on Celeron Haswell CPUs
Date: Fri, 25 Feb 2022 14:37:23 +0000	[thread overview]
Message-ID: <bug-104683-4-rJVVk2yN75@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104683-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104683

--- Comment #4 from Preston Crow <pc-gcc22 at crowcastle dot net> ---
I can see how it's documented, but many people reading that won't realize that
the instruction sets don't match all Haswell chips.  Simply adding a line below
that to say "Note: Some lower-end Haswell processors do not include all of the
above instruction sets."  And do the same for the others.  Then at least anyone
reading the documentation will immediately be aware of the potential problem
and hopefully avoid using them in inappropriate situations.

      parent reply	other threads:[~2022-02-25 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  2:22 [Bug other/104683] New: " pc-gcc22 at crowcastle dot net
2022-02-25  8:27 ` [Bug target/104683] " rguenth at gcc dot gnu.org
2022-02-25 10:32 ` rguenth at gcc dot gnu.org
2022-02-25 10:38 ` rguenth at gcc dot gnu.org
2022-02-25 14:37 ` pc-gcc22 at crowcastle dot net [this message]

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=bug-104683-4-rJVVk2yN75@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).