Verify that running in optimized mode while checking for use-after-dtor errors, does not generate tail call invocation of destructor. This avoids possible error where stack frame for the destructor is eliminated, making tracking down the errors more difficult.
|35 ↗||(On Diff #30966)|
Use @LINE to refer to line numbers in the test case.
|37 ↗||(On Diff #30966)|
You don't need a 'CHECK-OPT' if it's the same as 'CHECK'
|41 ↗||(On Diff #30966)|
Don't refer to the line numbers in other files, they will change.
Please rename the test to "use-after-dtor.cc". It's not really about tail calls, it's a general test of the use-after-dtor report.
|4 ↗||(On Diff #30981)|
Add a test at -O2
|35 ↗||(On Diff #30981)|
Maybe remove the space after "main" to make this more robust, in case, on some other platform, the symbolizer would add () after main.
|39 ↗||(On Diff #30981)|
Remove () for the same reason