forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 18
Compiler infinite loop with AutoFDO and GCOV #2172
Copy link
Copy link
Open
Labels
Compiler hauntedThe compiler is haunted, please fix your compiler.The compiler is haunted, please fix your compiler.[BUG] llvmA bug that should be fixed in upstream LLVMA bug that should be fixed in upstream LLVM[FEATURE] AutoFDORelated to building the kernel with Automatic Feedback Directed OptimizationRelated to building the kernel with Automatic Feedback Directed Optimization
Description
Activity
Metadata
Metadata
Assignees
Labels
Compiler hauntedThe compiler is haunted, please fix your compiler.The compiler is haunted, please fix your compiler.[BUG] llvmA bug that should be fixed in upstream LLVMA bug that should be fixed in upstream LLVM[FEATURE] AutoFDORelated to building the kernel with Automatic Feedback Directed OptimizationRelated to building the kernel with Automatic Feedback Directed Optimization
@yabinc may be able to provide more info (such as what translation unit we saw this in, what the last known good LLVM SHA and first known bad LLVM SHA were).
In at least one of our kernel builds for Android, enabling GCOV caused the compiler to enter an infinite loop. We were able to quickly work around this by filtering the profile data for a few symbols, but I don't consider this a viable long term solution and worry that this might pop up again and not just for GCOV.