Displaying 2 results from an estimated 2 matches for "hasuselist".
2016 Sep 24
4
RFC: ConstantData should not have use-lists
...3).
3. (Optional) Remove use-lists from other non-GlobalValue Constants
that do not reference any GlobalValues. This would require some
sort of magic in, e.g., ConstantVector to conditionally have a
use-list. Call sites of API like Value::use_begin would have to
check for Value::hasUseList.
4. (Optional) Remove the ref-count from ConstantData (and, potentially,
other use-list-free Constants). This would eliminate ref-count
traffic, but would also require checking at call sites before using
any use-list-related API.
Feedback
========
- Does anyone disagree with this g...
2016 Sep 24
2
RFC: ConstantData should not have use-lists
...ctorWithGlobalRef (which can/must transitively reference GlobalValue), right? (And also for ConstantStruct, ConstantArray, and ConstantExpr, etc.)
I hadn't considered that, and it seems worth thinking about. I'm unsure whether using isa<>() would really be cleaner than using Value::hasUseList; and it would certainly be intrusive. Do you see any concrete benefits?
One possible long-term thing (after #4)... we could add ConstantDataUser (vs. User), which can only reference a Constant-with-no-GlobalValue, and has operands the size of a pointer. Obviously nice to save on operand-size, bu...