public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: sedat.dilek@gmail.com, Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Ian Rogers <irogers@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [Linux-6.11-rc4] perf BROKEN with LLVM/Clang 19.1.0-rc3
Date: Thu, 22 Aug 2024 12:34:26 -0300	[thread overview]
Message-ID: <ZsdaglSCDdFoBcjQ@x1> (raw)
In-Reply-To: <CAM9d7cgHCJgJb10zaNt7b1Dy=4raiv+a1C1GwrVptNz5Uh+SNg@mail.gmail.com>

On Wed, Aug 21, 2024 at 01:37:25PM -0700, Namhyung Kim wrote:
> Hello,
> 
> On Wed, Aug 21, 2024 at 12:37 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
> >
> > As a workaround:
> >
> > dileks@iniza:~/src/linux/git$ git diff
> > diff --git a/tools/perf/util/setup.py b/tools/perf/util/setup.py
> > index 142e9d447ce7..db45e6fe7a21 100644
> > --- a/tools/perf/util/setup.py
> > +++ b/tools/perf/util/setup.py
> > @@ -63,6 +63,8 @@ cflags = getenv('CFLAGS', '').split()
> > cflags += ['-fno-strict-aliasing', '-Wno-write-strings',
> > '-Wno-unused-parameter', '-Wno-redundant-decls' ]
> > if cc_is_clang:
> >     cflags += ["-Wno-unused-command-line-argument" ]
> > +    cflags += ["-Wno-cast-function-type-mismatch" ]
> > +
> > else:
> >     cflags += ['-Wno-cast-function-type' ]
> >
> 
> Thanks for the fix.  I wasn't aware of the issue and the fix
> looks good to me.  I'll add it to perf-tools if nobody objects.

It doesn't work, please see the alternative patch I sent, if you try
that in a clang that doesn't have that warning option, it will fail,
i.e. clang 18 fails with the above patch.

- Arnaldo
 
> Thanks,
> Namhyung
> 
> 
> > dileks@iniza:~/src/linux/git$ ~/bin/perf -vv
> > perf version 6.11.0-rc4
> >                 dwarf: [ on  ]  # HAVE_DWARF_SUPPORT
> >    dwarf_getlocations: [ on  ]  # HAVE_DWARF_GETLOCATIONS_SUPPORT
> >         syscall_table: [ on  ]  # HAVE_SYSCALL_TABLE_SUPPORT
> >                libbfd: [ OFF ]  # HAVE_LIBBFD_SUPPORT
> >            debuginfod: [ on  ]  # HAVE_DEBUGINFOD_SUPPORT
> >                libelf: [ on  ]  # HAVE_LIBELF_SUPPORT
> >               libnuma: [ on  ]  # HAVE_LIBNUMA_SUPPORT
> > numa_num_possible_cpus: [ on  ]  # HAVE_LIBNUMA_SUPPORT
> >               libperl: [ on  ]  # HAVE_LIBPERL_SUPPORT
> >             libpython: [ on  ]  # HAVE_LIBPYTHON_SUPPORT
> >              libslang: [ on  ]  # HAVE_SLANG_SUPPORT
> >             libcrypto: [ on  ]  # HAVE_LIBCRYPTO_SUPPORT
> >             libunwind: [ on  ]  # HAVE_LIBUNWIND_SUPPORT
> >    libdw-dwarf-unwind: [ on  ]  # HAVE_DWARF_SUPPORT
> >           libcapstone: [ on  ]  # HAVE_LIBCAPSTONE_SUPPORT
> >                  zlib: [ on  ]  # HAVE_ZLIB_SUPPORT
> >                  lzma: [ on  ]  # HAVE_LZMA_SUPPORT
> >             get_cpuid: [ on  ]  # HAVE_AUXTRACE_SUPPORT
> >                   bpf: [ on  ]  # HAVE_LIBBPF_SUPPORT
> >                   aio: [ on  ]  # HAVE_AIO_SUPPORT
> >                  zstd: [ on  ]  # HAVE_ZSTD_SUPPORT
> >               libpfm4: [ on  ]  # HAVE_LIBPFM
> >         libtraceevent: [ on  ]  # HAVE_LIBTRACEEVENT
> >         bpf_skeletons: [ on  ]  # HAVE_BPF_SKEL
> >  dwarf-unwind-support: [ on  ]  # HAVE_DWARF_UNWIND_SUPPORT
> >            libopencsd: [ OFF ]  # HAVE_CSTRACE_SUPPORT
> >
> > -Sedat-

  reply	other threads:[~2024-08-22 15:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 19:23 [Linux-6.11-rc4] perf BROKEN with LLVM/Clang 19.1.0-rc3 Sedat Dilek
2024-08-21 19:37 ` Sedat Dilek
2024-08-21 20:37   ` Namhyung Kim
2024-08-22 15:34     ` Arnaldo Carvalho de Melo [this message]
2024-08-22 14:26 ` Arnaldo Carvalho de Melo
2024-08-22 15:09   ` Arnaldo Carvalho de Melo
2024-08-22 17:02     ` Sedat Dilek
2024-08-22 17:12       ` Arnaldo Carvalho de Melo
2024-08-22 17:19         ` Arnaldo Carvalho de Melo
2024-08-22 17:31           ` Sedat Dilek
2024-08-22 17:40             ` Arnaldo Carvalho de Melo
2024-08-22 17:59               ` Sedat Dilek
2024-08-22 18:17                 ` Namhyung Kim
2024-08-22 18:20                   ` Arnaldo Carvalho de Melo
2024-08-22 18:29                     ` Sedat Dilek
2024-08-22 20:11                     ` Namhyung Kim
2024-08-22 20:26                       ` Arnaldo Carvalho de Melo
2024-08-22 20:30                         ` Namhyung Kim
2024-08-23 13:58                           ` Sedat Dilek
2024-08-23 15:03                             ` Namhyung Kim
2024-08-22 18:17                 ` Arnaldo Carvalho de Melo
2024-08-22 18:19                   ` Sedat Dilek

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=ZsdaglSCDdFoBcjQ@x1 \
    --to=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sedat.dilek@gmail.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