In addition to checking compiler flags, the front-end also examines the attributes of the destructor definition to ensure that the SanitizeMemory attribute is attached.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
What happens if the attribute is used with the "= default" destructor?
lib/CodeGen/CGClass.cpp | ||
---|---|---|
1483 | I think it would be cleaner to use CodegenFunction::SanOpts | |
test/CodeGenCXX/sanitize-dtor-callback.cpp | ||
22 ↗ | (On Diff #31250) | Maybe move this to a separate test file? This one gets cluttered; for example, tail call is a completely orthogonal issue and attribute test should not have to deal with it. |
25 ↗ | (On Diff #31250) | Remove {{^ }} to make the check stronger. |
test/CodeGenCXX/sanitize-dtor-callback.cpp | ||
---|---|---|
72 ↗ | (On Diff #31263) | extra lines? |
I think it would be cleaner to use CodegenFunction::SanOpts