Yet, Chrome has given up on using LLVM for V8 JIT exactly because its slowdown w... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		pjmlp on May 13, 2023 \| parent \| context \| favorite \| on: A whirlwind tour of the LLVM optimizer Yet, Chrome has given up on using LLVM for V8 JIT exactly because its slowdown wasn't worth the performance gains they were getting out of it. The ART team has taken a similar deciion regaring AOT/JIT toolchain for native code compilation. Adopting LLVM isn't always a success story.

plagiarist on May 13, 2023 [–]

They have probably made an informed decision. Instead of, "how hard can it be to write optimization passes and different architectures? Like one or two sprints?"

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact