[PATCH] D18827: Rework/enhance stack coloring data flow analysis.
Quentin Colombet via llvm-commits
llvm-commits at lists.llvm.org
Mon Apr 11 12:57:28 PDT 2016
qcolombet added inline comments.
================
Comment at: lib/CodeGen/StackColoring.cpp:179
@@ +178,3 @@
+ /// \returns True if inst contains a lifetime start or end
+ bool isLifetimeStartOrEnd(const MachineInstr &MI,
+ std::vector<int> *slots,
----------------
thanm wrote:
> As far as I know (take this with a grain of salt, since I am an LLVM newbie) the only way to end a lifetime is with a LIFETIME_END marker instruction. If you can think of a scenario where you might have both, then yes, this should definitely be changed. Let me know if you have a real example?
No, you’re right, for lifetime markers this cannot happen at the same time. I was thinking in term of live-range. Maybe add in the comment that we consider only lifetime end from LIFETIME_END instructions and thus, we cannot have both conditions (start and end) at the same time.
http://reviews.llvm.org/D18827
More information about the llvm-commits
mailing list