Subsequent patches will implement page-aliasing mode for x86_64, which
will initially only work for the primary heap allocator. We force
callback instrumentation to simplify the initial aliasing
implementation.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Transforms/Instrumentation/HWAddressSanitizer.cpp | ||
---|---|---|
489 | ClInstrumentWithCalls is per process global, Usually we add member like HWAddressSanitizer::InstrumentWithCalls and initialize it according to Cl flags and other parameters. |
Comment Actions
I'm concerned about losing test coverage of stack and globals in hwasan.
Could we keep both modes until page aliasing reaches feature parity?
As an alternative, we could setup aarch64 simulator testing, or even a native aarch64 builder/tester.
Comment Actions
Isn't aarch64 already tested? I see several REQUIRES: aarch64-target-arch or REQUIRES: android in tests already.
ClInstrumentWithCalls is per process global,
TargetTriple is per module
Usually we add member like HWAddressSanitizer::InstrumentWithCalls and initialize it according to Cl flags and other parameters.