[PATCH] D97673: [RFC] [[Coroutine] [Debug] Salvage dbg.value at O2

Xun Li via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Sun Apr 18 10:42:18 PDT 2021


lxfind added a comment.

> Previously all `dbg.value`s would be lost after CoroSplit pass. `dbg.value` is debug info compiler produced under optimization. This patch wants to remain as many `dbg.value` as possible while it don't want to change the layout of frame for debug info.

Why would all `dbg.value`s be lost after CoroSplit pass? As long as they are in the resume code path, they would be kept in the .resume function, right?
I also tried to run coro-split on coro-debug-dbg.values-O2.ll, I do see a ton of dbg.value in the generate functions even without this patch.
Could you elaborate what is the exact problem, perhaps ideally with an example?


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D97673/new/

https://reviews.llvm.org/D97673



More information about the llvm-commits mailing list