Displaying 3 results from an estimated 3 matches for "8ce4d4ae".
2011 Jul 26
0
[LLVMdev] Linking opaque types
On Mon, Jul 25, 2011 at 9:36 PM, Chris Lattner <clattner at apple.com> wrote:
> On Jul 25, 2011, at 8:52 AM, Anton Lokhmotov wrote:
> > There is an issue with representing opaque types in LLVM IR modules: if
> two
> > modules are using the same opaque type (which is only going to be
> > specialised at some later stage), it is only identified by its name. But
>
2011 Jul 26
2
[LLVMdev] Linking opaque types
On Jul 25, 2011, at 8:52 AM, Anton Lokhmotov wrote:
> There is an issue with representing opaque types in LLVM IR modules: if two
> modules are using the same opaque type (which is only going to be
> specialised at some later stage), it is only identified by its name. But
> the current module linker "resolves" this as if there is a name clash, and
> one of that opaque
2011 Jul 26
3
[LLVMdev] Linking opaque types
...you mean. LLVM is perfectly fine with opaque structs so long as you don't "deference" them, GEP into them, need their size, etc.
-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110725/8ce4d4ae/attachment.html>