[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fXK-owoydNf0_AYFhNPnxAgoy5G9smQ6+LtbrUh6W2wDQ@mail.gmail.com>
Date: Tue, 20 Jan 2026 15:42:42 -0800
From: Ian Rogers <irogers@...gle.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Namhyung Kim <namhyung@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, James Clark <james.clark@...aro.org>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, Clark Williams <williams@...hat.com>,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH 0/4] Fixes for gcc 16.0.1
On Tue, Jan 20, 2026 at 2:11 PM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> From: Arnaldo Carvalho de Melo <acme@...hat.com>
>
> Hi,
>
> A bunch of fixes for recent gcc versions,
>
> - Arnaldo
Reviewed-by: Ian Rogers <irogers@...gle.com>
These look like the least bad resolutions to the new warnings, thanks!
Ian
> Arnaldo Carvalho de Melo (4):
> perf tests sw-clock: Mark the volatile tmp variable as __maybe_unused
> perf trace: Deal with compiler const checks
> perf list: Don't write to const memory
> perf list: Signal changing const memory is ok
>
> tools/perf/builtin-trace.c | 2 +-
> tools/perf/tests/sw-clock.c | 3 ++-
> tools/perf/util/print-events.c | 15 ++++++---------
> 3 files changed, 9 insertions(+), 11 deletions(-)
>
> --
> 2.52.0
>
Powered by blists - more mailing lists