All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: Eduard Zingerman <eddyz87@gmail.com>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@kernel.org>,
	bpf <bpf@vger.kernel.org>
Subject: Re: bpf selftest pyperf180.c compilation failure with latest last llvm18 (in development)
Date: Wed, 8 Nov 2023 18:58:20 -0800	[thread overview]
Message-ID: <ec34f1d5-2b57-4f0f-9edd-070bb98a2b6c@linux.dev> (raw)
In-Reply-To: <98d0330ecb6b3b1a366de5395dbef7ab7758288a.camel@gmail.com>


On 11/8/23 5:20 PM, Eduard Zingerman wrote:
> On Wed, 2023-11-08 at 12:05 -0800, Alexei Starovoitov wrote:
> [...]
>> The algorithm doesn't look simple.
>> Even if we change llvm to do this, it's not clear whether
>> the verifier will be able to consume such code.
> Actually, I don't think that trampoline jumps could cause any trouble.
>
>> imo it's too much effort to address a non-issue.
>> I'd just adjust the pyperf180.c test.
> Ok, I'll drop this. Thank you for taking a look.

Thanks Eduard for doing analysis for this! I will send
a patch soon to fix selftest failure issue.


      reply	other threads:[~2023-11-09  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  3:58 bpf selftest pyperf180.c compilation failure with latest last llvm18 (in development) Yonghong Song
2023-11-08  2:13 ` Eduard Zingerman
2023-11-08 20:05   ` Alexei Starovoitov
2023-11-09  1:20     ` Eduard Zingerman
2023-11-09  2:58       ` Yonghong Song [this message]

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=ec34f1d5-2b57-4f0f-9edd-070bb98a2b6c@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=martin.lau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.