Displaying 3 results from an estimated 3 matches for "layoutbut".
2008 Sep 15
1
[LLVMdev] Casting between address spaces and address space semantics
...he information as a target description string like we do for
> ABI information. I just don't want to end up with too many objects that
> describe the machine. One can argue that we shouldn't pollute the
> TargetData since it describes the ABI alignment, size, and object
> layoutbut I feel that this data fits naturally there. If you and other
> people feel it is cleaner with a separate pass, I'm fine with it.
Perhaps encoding it in TargetData makes sense. However, I was avoiding this
for now, since Chris commented a while back that he wanted to have it in
TargetData...
2008 Aug 12
0
[LLVMdev] Casting between address spaces and address space semantics
...e could encode the information as a target description string like we
do for ABI information. I just don't want to end up with too many
objects that describe the machine. One can argue that we shouldn't
pollute the TargetData since it describes the ABI alignment, size,
and object layoutbut I feel that this data fits naturally there. If
you and other people feel it is cleaner with a separate pass, I'm fine
with it.
I want to treat my next point with some delicacy as I don't want to
start a religious war. I just want to get clarification from the
community on the use...
2008 Aug 11
2
[LLVMdev] Casting between address spaces and address space semantics
Hi Mon Ping,
> I don't have a problem having another class, TargetAddrSpace, to store this
> information. However, I don't think it make sense being a standalone pass.
> Address spaces seems to part of the TargetData and it seems more natural
> to ask the TargetData to return the TargetAddrSpace object (similar to
> struct layout) to describe the relationships