Details
- Reviewers
kcc samsonov - Commits
- rGd02ce13bd97c: SanitizerCoverage: Use `createSanitizerCtor` to create ctor and call init
rG5bc0feb3deaf: SanitizerCoverage: Use `createSanitizerCtor` to create ctor and call init
rL236951: SanitizerCoverage: Use `createSanitizerCtor` to create ctor and call init
rL236780: SanitizerCoverage: Use `createSanitizerCtor` to create ctor and call init
Diff Detail
Event Timeline
lib/Transforms/Instrumentation/SanitizerCoverage.cpp | ||
---|---|---|
197–198 | Isn't this function supposed to be created in createSanitizerCtor? |
lib/Transforms/Instrumentation/SanitizerCoverage.cpp | ||
---|---|---|
197–198 | Good catch, thanks! I will include it in the next revision. It needs a test to check init function is called from module ctor, as well as renaming createSanitizerCtor below. |
- createSanitizerCtor renamed to createSanitizerCtorAndInitFunctions to match with changes in D8777
- SanCovModuleInit was initialized with checkInterfaceFunction by mistake; this is already done by createSanitizerCtorAndInitFunctions
Turns out, there is already a test checking module ctor, and call to init function, in test/Instrumentation/SanitizerCoverage/coverage.ll.
lib/Transforms/Instrumentation/SanitizerCoverage.cpp | ||
---|---|---|
272 | (or just use std::ignore) |
Isn't this function supposed to be created in createSanitizerCtor?