public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at eckner dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100758] __builtin_cpu_supports does not (always) detect "sse2" Date: Wed, 26 May 2021 09:46:27 +0000 [thread overview] Message-ID: <bug-100758-4-u1J6FebcRH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100758-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100758 --- Comment #4 from Erich Eckner <gcc at eckner dot net> --- Created attachment 50871 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50871&action=edit cpuid probing Does the attached program yield, what you need? (Sry, I'm quite unfamiliar with asm in gcc) It gives: 00000001 746e6543 736c7561 48727561 000006d0 00000800 00004181 a7c9bbff and 0000000a 746e6543 736c7561 48727561 000006fa 00010800 008863a9 afc9fbff on the two machines, respectively.
next prev parent reply other threads:[~2021-05-26 9:46 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 18:37 [Bug c/100758] New: " gcc at eckner dot net 2021-05-26 7:57 ` [Bug target/100758] " marxin at gcc dot gnu.org 2021-05-26 9:12 ` gcc at eckner dot net 2021-05-26 9:23 ` marxin at gcc dot gnu.org 2021-05-26 9:46 ` gcc at eckner dot net [this message] 2021-05-26 9:54 ` rguenth at gcc dot gnu.org 2021-05-26 10:09 ` marxin at gcc dot gnu.org 2021-05-26 10:13 ` gcc at eckner dot net 2021-06-01 13:26 ` marxin at gcc dot gnu.org 2023-01-27 20:48 ` iam at valdikss dot org.ru 2023-02-01 14:03 ` marxin at gcc dot gnu.org 2023-02-01 14:23 ` iam at valdikss dot org.ru 2023-02-01 14:32 ` marxin at gcc dot gnu.org 2023-02-09 10:50 ` cvs-commit at gcc dot gnu.org 2023-02-09 11:40 ` jakub at gcc dot gnu.org 2023-02-09 11:47 ` marxin at gcc dot gnu.org 2023-02-09 12:22 ` jakub at gcc dot gnu.org 2023-02-09 16:22 ` gcc at eckner dot net 2023-02-09 16:37 ` jakub at gcc dot gnu.org 2023-02-09 16:45 ` cvs-commit at gcc dot gnu.org 2023-02-09 20:37 ` gcc at eckner dot net 2023-02-09 21:35 ` iam at valdikss dot org.ru 2023-02-10 8:27 ` marxin at gcc dot gnu.org 2023-02-10 9:45 ` jakub at gcc dot gnu.org 2023-02-20 9:50 ` Mayshao-oc at zhaoxin dot com 2023-03-19 5:29 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:21 ` cvs-commit at gcc dot gnu.org
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-100758-4-u1J6FebcRH@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: linkBe 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).