mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-18 02:06:41 +00:00
842b57b775
Whereas it is UB in terms of the standard to delete an array of objects via pointer whose static type doesn't match its dynamic type, MSVC supports an extension allowing to do it. Aside from array deletion not working correctly in the mentioned case, currently not having this extension implemented causes clang to generate code that is not compatible with the code generated by MSVC, because clang always puts scalar deleting destructor to the vftable. This PR aims to resolve these problems. It was reverted due to link time errors in chromium with sanitizer coverage enabled, which is fixed by https://github.com/llvm/llvm-project/pull/131929 . The second commit of this PR also contains a fix for a runtime failure in chromium reported in https://github.com/llvm/llvm-project/pull/126240#issuecomment-2730216384 . Fixes https://github.com/llvm/llvm-project/issues/19772
These are tests for instrumentation based profiling. This specifically means the -fprofile-instr-generate and -fprofile-instr-use driver flags. Tests in this directory should usually test both: - the generation of instrumentation (-fprofile-instr-generate), and - the use of profile data from instrumented runs (-fprofile-instr-use). In order to test -fprofile-instr-use without actually running an instrumented program, .profdata files are checked into Inputs/. The input source files must include a main function such that building with -fprofile-instr-generate and running the resulting program generates the same .profdata file that is consumed by the tests for -fprofile-instr-use. Even tests that only check -fprofile-instr-use should include such a main function, so that profile data can be regenerated as the .profdata file format evolves.