3 ms·
The bug shows up without asan. We literally tripped over it in production with code compiled with "clang -O2".
by cperciva 6y ago
The bug shows up without asan. We literally tripped over it in production with code compiled with "clang -O2".
- drivebycomment 6y agoThen I agree that this is surprising. That means clang/llvm is not modeling set/longjmp correctly in general and that is not acceptable as a C compiler.
- scatters 6y agoThat's apparent from your ticket (which is marked as a duplicate) but on the one you linked to, all the offending compiler lines contain asan. Is there a chance this is impacting prioritization?
- cperciva 6y agoCould be. I'm not an LLVM developer so I don't know how they prioritize issues.