public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chiitoo at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/110260] New: Multiple applications misbehave when compiled with -march=znver4
Date: Wed, 14 Jun 2023 21:22:21 +0000	[thread overview]
Message-ID: <bug-110260-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110260
           Summary: Multiple applications misbehave when compiled with
                    -march=znver4
           Product: gcc
           Version: 13.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: chiitoo at gentoo dot org
  Target Milestone: ---

While hunting for the cause for a stack alignment issue in Wine [1], it started
to look more and more that '-march=znver4' is at least related to the issue.

I had compiled a few hundred other packages mistakingly with certain testing
flags in between building Wine and the mingw-toolchain, and noticed a certain
issue related to KWin disappear [2].

The issue came back the next day, after resting X11, and it took me a while to
realise what had happened.  I saw from my build logs that KWin was one of those
packages that I had compiled with the testing C{XX}FLAGS (-march=x86-64 -O2
-g), and I had then later compiled it again with the usual flags (-march=znver4
-O2 -fomit-frame-pointer -pipe -mindirect-branch=thunk), and so I did some test
builds with -march=x86-64 and -march=znver3 and the problem goes away.

There's at least one more recent issue with my LXQt panel task manager widget,
but I'm not sure yet if this will make that go away as well.

Let me know if I can help pinpoint the issue more, or/and confirm this to be a
GCC issue or not.

Next I'm thinking of trying to see if I can spot one or more of the
instructions do it that is not included with znver3 per the x86-Options
documentation [3].

(By the by, is ADCX a typo of ADX?  I see -madx as an option but only one use
of it otherwise, and no -adcx as an option and lots of mentions of it... but
perhaps I'm not reading them correct-like.)

Thank you!


1. https://bugs.winehq.org/show_bug.cgi?id=55007
2. https://bugs.kde.org/show_bug.cgi?id=469426
3. https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html

             reply	other threads:[~2023-06-14 21:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 21:22 chiitoo at gentoo dot org [this message]
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
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@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).