public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brjd_epdjq36 at kygur dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107551] __builtin_cpu_supports returns a negative integer for "x86-64"
Date: Mon, 05 Dec 2022 11:28:47 +0000	[thread overview]
Message-ID: <bug-107551-4-ZgjwtMMuKX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107551-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Brjd <brjd_epdjq36 at kygur dot com> ---
Maybe it is better if we test it in the next release 12.3 or 13.1 since now the
test will be correct, ok, but when building source with the compiler, it will
not make any difference and make no problems at all?

  parent reply	other threads:[~2022-12-05 11:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 13:00 [Bug c++/107551] New: gcc 12.2 test fails brjd_epdjq36 at kygur dot com
2022-11-07 13:35 ` [Bug c++/107551] " brjd_epdjq36 at kygur dot com
2022-11-07 15:51 ` [Bug target/107551] g++ " pinskia at gcc dot gnu.org
2022-11-07 16:08 ` brjd_epdjq36 at kygur dot com
2022-11-07 16:10 ` brjd_epdjq36 at kygur dot com
2022-11-08  9:23 ` rguenth at gcc dot gnu.org
2022-11-08  9:49 ` brjd_epdjq36 at kygur dot com
2022-11-21 12:28 ` marxin at gcc dot gnu.org
2022-11-24 23:31 ` brjd_epdjq36 at kygur dot com
2022-11-25 11:46 ` [Bug target/107551] __builtin_cpu_is returns a negative integer for x86-64 marxin at gcc dot gnu.org
2022-11-25 11:46 ` marxin at gcc dot gnu.org
2022-11-29  9:15 ` [Bug target/107551] __builtin_cpu_supports returns a negative integer for "x86-64" brjd_epdjq36 at kygur dot com
2022-11-30 12:22 ` marxin at gcc dot gnu.org
2022-12-02 13:11 ` marxin at gcc dot gnu.org
2022-12-05 11:24 ` brjd_epdjq36 at kygur dot com
2022-12-05 11:28 ` brjd_epdjq36 at kygur dot com [this message]
2022-12-05 11:30 ` marxin at gcc dot gnu.org
2022-12-05 11:54 ` brjd_epdjq36 at kygur dot com
2022-12-05 12:08 ` marxin at gcc dot gnu.org
2022-12-05 13:22 ` brjd_epdjq36 at kygur dot com
2022-12-05 13:26 ` marxin at gcc dot gnu.org
2022-12-05 15:02 ` brjd_epdjq36 at kygur dot com
2022-12-05 15:04 ` brjd_epdjq36 at kygur dot com
2022-12-05 15:17 ` brjd_epdjq36 at kygur dot com
2022-12-09  9:21 ` cvs-commit at gcc dot gnu.org
2022-12-09  9:29 ` marxin at gcc dot gnu.org
2022-12-09 13:25 ` cvs-commit at gcc dot gnu.org
2022-12-09 13:26 ` marxin 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-107551-4-ZgjwtMMuKX@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).