jasonmolenda wrote:
This all looks reasonable to me. It's good to have a test that debugserver is
expediting the stack memory needed for a simple frame-chain stack walk, without
sending any packets. It's critical for performance but untested. This C-based
test case for different types of local variables (combining stack and heap
memory access to print summaries) is a good start. The use of a `volatile`
register to try to suppress compiler optimization isn't needed - at `-O0` the
compiler will generate code even when utterly unnecessary. I've written test
cases that look like
```
int main() {
int c = 10;
c++;
c++;
c++
return c;
}```
https://github.com/llvm/llvm-project/pull/205897
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
