http://llvm.org/bugs/show_bug.cgi?id=4971
Ãscar Fuentes <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Ãscar Fuentes <[email protected]> 2009-09-16 20:21:23 --- After working for a while on this, found that the problem happens on x86_64-linux but not on x86-mingw, that is related to opaque types used by function types, which ends being invalid or dangling pointers. When an opaque type is resolved and a function type that references it ends being a type that already exists, the problem arises. I tried to replicate the problem outside of my compiler with no luck. As this may be a bug on my side, I'll close the bug. -- Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
