Displaying 3 results from an estimated 3 matches for "8be4e173".
Did you mean:
80ede173
2011 Jul 27
1
[LLVMdev] Linking opaque types
...range!"), function getElementType, file /Users/talin/Projects/llvm/include/llvm/DerivedTypes.h, line 268.
>
Sounds like a bug, thanks.
-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110727/8be4e173/attachment.html>
2011 Jul 27
0
[LLVMdev] Linking opaque types
On Tue, Jul 26, 2011 at 11:01 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On Jul 26, 2011, at 8:11 AM, Talin wrote:
>
>
>> If that's true, then it means that we're back to the case where every type
>> has to be fully defined down to the leaf level.
>>
>>
>> I'm not sure what you mean. LLVM is perfectly fine with opaque structs
2011 Jul 27
2
[LLVMdev] Linking opaque types
On Jul 26, 2011, at 8:11 AM, Talin wrote:
>>
>> If that's true, then it means that we're back to the case where every type has to be fully defined down to the leaf level.
>
> I'm not sure what you mean. LLVM is perfectly fine with opaque structs so long as you don't "deference" them, GEP into them, need their size, etc.
>
> Let me try with