Finding what information is know about a value from a use is generally useful and can be done quickly.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/IR/Instructions.cpp | ||
---|---|---|
387 | Please explain this in a comment at the beginning of the function. Also comment the magic constants. | |
llvm/lib/Transforms/Utils/KnowledgeRetention.cpp | ||
306 | Is this more for testing or do you expect another use case? | |
llvm/unittests/Transforms/Utils/KnowledgeRetentionTest.cpp | ||
489 | What is the runtime we are expecting here? |
llvm/lib/IR/Instructions.cpp | ||
---|---|---|
387 | added comments and messages to assets. hope its enough. | |
llvm/lib/Transforms/Utils/KnowledgeRetention.cpp | ||
306 | there is another use case for getBundleOpInfoForOperand coming in D73404 in the implementation of Value::dropDroppableUses. and i think that getKnowledgeFromOperandInAssume is a generally useful functionality especially with the getKnowledgeFromUseInAssume. you can gather all knowledge we have on a value by going through the use list. | |
llvm/unittests/Transforms/Utils/KnowledgeRetentionTest.cpp | ||
489 | On my computer the average for AssumeQueryAPI.getKnowledgeFromUseInAssume is around 116 ms do you think it is reasonable ? or the test should be reduced in size. |
Can you add a short comment here as well please.