appujee

> The main problem fixed with clang 16 for arm64 (and probably x86 as well, but I haven't checked) was resolving dependencies and generating proper IR. AFAIK that is mostly...

Added in bionic https://android-review.googlesource.com/c/platform/bionic/+/3063184

Does the recent update in: https://github.com/riscv/riscv-v-spec/commit/e2ccd0548d6ce0b769ecdd1ce2521c19e26c39de address this issue?

What are the instructions to ssh into Lichee Pi 4A RISC-V board?

The only difference i see between clang-17 and clang-18 is the llvm.lifetime.start.p0 and llvm.lifetime.end.p0 markers https://godbolt.org/z/qGhT5ne7P That does affect the schedule of instruction in the final assembly. https://godbolt.org/z/vo7Mj8Kz9 Left side...

Should we create a similar bug for [binutils](https://sourceware.org/bugzilla/) ?

vptr check is [part of ubsan](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html), not sure why enabling ubsan doesn't trigger it. You might want to open a bug in [llvm-project/issues](https://github.com/llvm/llvm-project/issues) for clarification

> If I turn on the compilation options below, a crash will occur： > -fsanitize=undefined -fno-sanitize-recover=undefined > But when I turned off the vpr check, everything was fine： > -fsanitize=undefined...

Are you using fvisibility flag somewhere? there is a similar bug reported in: https://bugs.llvm.org/show_bug.cgi?id=39191

As the current behavior of vptr relates to open source implementation of this sanitizer, it is better to create an issue in the [llvm-project/issues](https://github.com/llvm/llvm-project/issues) repo.