public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110260] Multiple applications misbehave when compiled with -march=znver4 Date: Wed, 14 Jun 2023 21:54:42 +0000 [thread overview] Message-ID: <bug-110260-4-t2ByCvsSbH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110260-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110260 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjames at gcc dot gnu.org --- Comment #2 from Sam James <sjames at gcc dot gnu.org> --- The case I've looked at the most is KWin (https://bugs.gentoo.org/895750) where we narrowed it down to https://bugs.kde.org/show_bug.cgi?id=460572#c28 with: """ To emphasise: - -O2 -march=x86-64-v3 works - -O2 -march=x86-64-v4 (or -march=rocketlake) triggers it """ It may not be the same as Chiitoo's bug here, but it probably is given the symptoms are the same & both likely involve AVX512. I couldn't reproduce it on my machine with AVX512 (only one machine, Tiger Lake) and couldn't really do any more at that point. I guess a good start would be seeing what the minimal file(s) required to break kwin are w/ -march=znver4.
next prev parent reply other threads:[~2023-06-14 21:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-14 21:22 [Bug other/110260] New: " chiitoo at gentoo dot org 2023-06-14 21:28 ` [Bug target/110260] " pinskia at gcc dot gnu.org 2023-06-14 21:54 ` sjames at gcc dot gnu.org [this message] 2023-06-15 6:32 ` rguenth at gcc dot gnu.org 2023-06-15 7:01 ` amonakov at gcc dot gnu.org 2023-06-15 7:04 ` rguenth at gcc dot gnu.org 2023-06-15 7:08 ` amonakov at gcc dot gnu.org 2023-06-15 9:53 ` [Bug target/110260] Multiple applications misbehave at runtime " chiitoo at gentoo dot org 2023-06-15 11:17 ` chiitoo at gentoo dot org 2023-06-15 18:06 ` zfigura at codeweavers dot com 2023-06-15 19:48 ` amonakov at gcc dot gnu.org 2023-06-15 21:55 ` zfigura at codeweavers dot com
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-110260-4-t2ByCvsSbH@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).