From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Peter Oberparleiter <oberpar@linux.ibm.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>
Cc: "Mikhail Zaslonko" <zaslonko@linux.ibm.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"Pavel Tikhomirov" <ptikhomirov@virtuozzo.com>,
"Vasileios Almpanis" <vasileios.almpanis@virtuozzo.com>
Subject: Re: [PATCH v2] gcov: use atomic counter updates to fix concurrent access crashes
Date: Wed, 22 Apr 2026 23:26:21 +0200 [thread overview]
Message-ID: <f181b798-eedd-493e-bb0f-7434198c4f3a@virtuozzo.com> (raw)
In-Reply-To: <20260422125112.3583649-2-khorenko@virtuozzo.com>
https://sashiko.dev/#/patchset/20260422125112.3583649-1-khorenko%40virtuozzo.com
> The kernel supports gcc versions down to 8.1.0, but the -fprofile-update=prefer-atomic compiler
flag was introduced in gcc 11.
-fprofile-update=prefer-atomic has been available since GCC 7.1.0 (May 2017).
https://github.com/gcc-mirror/gcc/blob/releases/gcc-7.1.0/gcc/common.opt#L1981-L1995
<<<<<<<<<<<<<<<<<
EnumValue
Enum(profile_update) String(prefer-atomic) Value(PROFILE_UPDATE_PREFER_ATOMIC)
>>>>>>>>>>>>>>>>>
So any GCC that can build the current kernel accepts -fprofile-update=prefer-atomic.
--
Best regards,
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
next prev parent reply other threads:[~2026-04-22 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 12:51 [PATCH v2 0/1] gcov: use -fprofile-update=prefer-atomic to fix concurrent access crashes Konstantin Khorenko
2026-04-22 12:51 ` [PATCH v2] gcov: use atomic counter updates " Konstantin Khorenko
2026-04-22 21:26 ` Konstantin Khorenko [this message]
2026-04-28 20:56 ` Arnd Bergmann
2026-05-07 13:31 ` Peter Oberparleiter
2026-05-07 13:43 ` Arnd Bergmann
2026-05-08 19:48 ` Andrew Morton
2026-05-09 11:50 ` Konstantin Khorenko
2026-05-09 14:36 ` Konstantin Khorenko
2026-05-09 15:14 ` Arnd Bergmann
2026-05-11 9:43 ` Konstantin Khorenko
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=f181b798-eedd-493e-bb0f-7434198c4f3a@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=ojeda@kernel.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=vasileios.almpanis@virtuozzo.com \
--cc=zaslonko@linux.ibm.com \
/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