cmd/compile: excessive instrumentation for libFuzzer #53760
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
fuzz
Issues related to native fuzzing support
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Performance
Milestone
When compiled with
We get a call to
runtime.libfuzzerTraceConstCmp1
, which seems unnecessary.This happens because we add (in the order pass):
But then we add instrumentation to all integer comparisons (in the walk pass):
I don't think we need to rewrite the internal libfuzzer counter overflow check to use the runtime comparison function. Only user comparisons should be so treated. I guess it technically doesn't hurt, but it will be slow.
@kyakdan
The text was updated successfully, but these errors were encountered: