[llvm-dev] Problem with local context getType() == global context getType()
John Criswell via llvm-dev
llvm-dev at lists.llvm.org
Tue Aug 25 17:18:10 PDT 2015
On 8/25/15 10:28 AM, koffie drinker via llvm-dev wrote:
> I'm experiencing a weird problem with llvm 3.7(rc2/rc3) that did not
> occur in llvm 3.6.2
> I created a bug for it: https://llvm.org/bugs/show_bug.cgi?id=24521
> I'm building a app where multiple code gen can happen in parallel. The
> documentation state that I need to use separate context. Each thread
> has it's own context.
> When code generating a constant number I use the *InContext() calls to
> create the types. The assert fails since the optimizer replaces some
> numbers with a global type. The values are equal but the types are
> not. I did patch some calls to compare on getTypeID() but got another
> assert a couple of days later in another source file.
It sounds like the two values (or the types of the values) are in
different contexts. If you are creating the Types, make sure each type
is created in the correct context. If some LLVM API function is
creating the type for you, then it may be creating it in the wrong
context (i.e., you have found a bug) or the LLVM API function has to
assume a context (i.e., there is a limitation in the API for your
If you determine that it is a bug, you should file a bug report. If
it's a limitation, you should file an enhancement request.
Sorry I can't be more helpful than that; I haven't used LLVM 3.7 yet,
and I haven't used multiple contexts within a multi-threaded
application. These are educated guesses on my part.
> I needed 3.7 because of the LLVMAddGlobalMapping C api fixes.
> Could someone help me out ? Or point me in the right direction? I'm
> using the C api.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
Department of Computer Science, University of Rochester
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev