mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Howard Chu <howardchu95@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH 1/1] perf build: Require at least clang 16.0.6 to build BPF skeletons
Date: Thu, 10 Oct 2024 10:11:35 +0100	[thread overview]
Message-ID: <5f3f55a8-a378-4e16-8e5b-6fff329e75fd@linaro.org> (raw)
In-Reply-To: <bcf50648-3c7e-4513-8717-0d14492c53b9@linaro.org>



On 10/10/2024 10:00 am, James Clark wrote:
> 
> 
> On 10/10/2024 2:20 am, Arnaldo Carvalho de Melo wrote:
>> On Wed, Oct 9, 2024, 10:01 PM Namhyung Kim <namhyung@kernel.org> wrote:
>>
>>> On Tue, Oct 08, 2024 at 12:27:24AM -0700, Howard Chu wrote:
>>>> Hi Alan, Arnaldo and James,
>>>>
>>>> This problem was solved in [PATCH 0/2] perf trace: Fix support for the
>>>> new BPF feature in clang 12 (Link:
>>>>
>>> https://lore.kernel.org/linux-perf-users/20241007051414.2995674-1- 
>>> howardchu95@gmail.com/T/#t
>>> ),
>>>> sorry I forgot to cc you two.
>>>>
>>>> Alan's thought was correct. Thank you so much! :)
>>>
>>> It'd be great if any of you can test this change.  Now I only have
>>> machines with clang 16.
>>>
>>
>> I'll test this tomorrow.
>>
>> - Arnaldo
>>
>>>
>>> Thanks,
>>> Namhyung
>>>
>>>
>>
> 
> Tested with clang 15:
> 
> $ sudo perf trace -e write --max-events=100 -- echo hello
> 
>    0.000 ( 0.014 ms): echo/834165 write(fd: 1, buf: hello\10, count: 6)
>                                             =
> 
> Tested-by: James Clark <james.clark@linaro.org>
> 

Should have left this tag on the actual patch. Will re-post it there.


  reply	other threads:[~2024-10-10  9:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 12:24 Arnaldo Carvalho de Melo
2024-09-12 14:40 ` James Clark
2024-09-12 14:50   ` Arnaldo Carvalho de Melo
2024-09-12 15:00     ` James Clark
2024-09-13 10:20     ` James Clark
     [not found]       ` <CA+JHD936J-q0-7LANQ3aW2G-PEmFP8PnXQ-TF-AMs9MtrCqfew@mail.gmail.com>
2024-09-17 17:37         ` Howard Chu
2024-09-19  3:13           ` Howard Chu
2024-09-24  2:00             ` Howard Chu
2024-09-24  9:29               ` Alan Maguire
2024-09-24 18:45                 ` Howard Chu
2024-10-08  7:27                   ` Howard Chu
2024-10-10  1:01                     ` Namhyung Kim
     [not found]                       ` <CA+JHD93JgJL_4GJFcFUNu-FpNfFOoyDRJ7QuvO82M8G1EwM5pQ@mail.gmail.com>
2024-10-10  9:00                         ` James Clark
2024-10-10  9:11                           ` James Clark [this message]
2024-10-10 16:15                             ` Namhyung Kim
2024-10-11 19:06                           ` Arnaldo Carvalho de Melo

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=5f3f55a8-a378-4e16-8e5b-6fff329e75fd@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alan.maguire@oracle.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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

all inboxes | Powered by JetHome®