User Details
- User Since
- May 24 2017, 3:29 AM (266 w, 2 d)
Tue, Jun 28
Do we have some broad overview of the approach and the algorithm? It'd be a good idea put something like this in the description and eventually the commit message. (I searched for LLVM complex RFCs, buy couldn't find anything useful).
Mon, Jun 27
Revert to a previous version, which scanned all the memory
accesses in a block. Add a testcase showing why it's necessary.
May 9 2022
Apr 18 2022
Apr 15 2022
Fixed a bootstrap failure, there was a missing check for end iterator.
Apr 14 2022
Apr 13 2022
Should these lists contain only source tree headers or also generated header files? I'm not seeing arm_mve.h, for example.
Apr 12 2022
Apr 11 2022
Apr 6 2022
Updated to exclude unreachable blocks.
Apr 5 2022
Apr 4 2022
Apr 1 2022
Mar 31 2022
Mar 30 2022
Mar 29 2022
That's right, it's the order of increasing instruction addresses, corresponding to the basic block layout and the order of instructions in the basic block.
Mar 24 2022
Rebased.
Rebased
Updated on top of latest main, will commit it the following days, based on previous
acceptance, as it contains no non-trivial changes.
Updated on top of latest main, will commit it the following days, based on previous
acceptance, as it contains no non-trivial changes.
Updated on top of latest main and on top of D121017
Now https://bugs.chromium.org/p/chromium/issues/detail?id=1302998 should be fixed.
Mar 23 2022
Mar 11 2022
Ping.
Mar 7 2022
PIng?
Mar 4 2022
Brought forward, emitting epilogue would no be correct without this patch. A little bit of tests moved to the epilogues patch, no other changes.
Committing this change caused failures in the asan/hwasan regression tests. The reason was that emitting unwind info
in epilogues caused the unwind information in case like below:
foo: ... CSR saves ... CSR restores ret L: ... b <somewhere>
to no longer be accidentally correct for the region starting at L. That could be a miscompilation
if a throwing call somehow ends up in that region.