public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/57832] compiling sha-256 code (xz 5.0.5) generates false warnings when using -march=native on Atom CPU Date: Sun, 20 Nov 2022 03:50:58 +0000 [thread overview] Message-ID: <bug-57832-4-uIkmkJTrNt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57832 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Known to work| |13.0 Resolution|--- |FIXED CC| |law at gcc dot gnu.org --- Comment #8 from Jeffrey A. Law <law at gcc dot gnu.org> --- Seems to have been fixed on the trunk, most likely Richi's work from earlier this year.
next prev parent reply other threads:[~2022-11-20 3:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-05 18:59 [Bug c/57832] New: " olivier.pis.langlois at transport dot alstom.com 2021-03-26 22:16 ` [Bug middle-end/57832] " msebor at gcc dot gnu.org 2021-03-27 9:02 ` manu at gcc dot gnu.org 2021-03-27 21:32 ` msebor at gcc dot gnu.org 2021-03-28 11:17 ` manu at gcc dot gnu.org 2022-11-20 3:50 ` law at gcc dot gnu.org [this message] 2022-11-20 4:13 ` pinskia 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-57832-4-uIkmkJTrNt@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).