yuvald-sweet-security wrote:
Hey,
I didn't see this change on the [LLVM 20.1.0 Release
Notes](https://releases.llvm.org/20.1.0/docs/ReleaseNotes.html) - it would be
nice if you could add those in the future as a heads up.
Anyway, I got here after tracing a regression introduced in Clang 20 wi
yuvald-sweet-security wrote:
> Thanks @yuvald-sweet-security I am not sure whether I can add default v1->v3
> in llvm20 or not. But let me check anyway.
>
> Also, if the verification failure can be easily reproduced, could you submit
> the test case, we can do some analysis to see why and mayb
yuvald-sweet-security wrote:
@4ast perhaps you know who in LLVM can help with adding a "Changes to the BPF
Backend" section to the release notes, similar to how other backends have their
own sections?
https://github.com/llvm/llvm-project/pull/107008
yuvald-sweet-security wrote:
> @yuvald-sweet-security Could you share which kernel you are used for above
> testing?
I ran this on my host machine which is Windows with WSL, kernel
`6.6.75.1-microsoft-standard-WSL2`. However, I can see similar regressions on
pretty much every testing VM that
yuvald-sweet-security wrote:
@yonghong-song thank you for taking the time to help with this issue and
providing your suggestions, it’s greatly appreciated. I am also glad to hear
that asm barriers are no longer necessary, as they caused quite some trouble
for me in the past. However, I've enco
yuvald-sweet-security wrote:
> > Hey,
> > I didn't see this change on the [LLVM 20.1.0 Release
> > Notes](https://releases.llvm.org/20.1.0/docs/ReleaseNotes.html) - it would
> > be nice if you could add those in the future as a heads up.
> > Anyway, I got here after tracing a regression in eBPF
