llvm dev - May 2012 - [LLVMdev] pseudo instructions not removed error

Hi,

I'm having problems when trying to JIT IR generated from C++ with clang. My
code resides in a dynamically loaded shared object, and crashes when I call
getPointerToFunction, claiming that it encountered a pseudo instruction.
Interestingly, a very similar code that run as a separate executable JITing the
same IR works fine. Note that I have not have modified LLVM. Any suggestions
what could cause this behavior?

Eran.

For anyone encountering this problem in the future, the cause of this
problem was debugging symbols (-g) given to clang when generating IR.

On 20/05/2012 12:21, "Weiss, Eran" <Eran.Weiss at emc.com>
wrote:
>Hi,
>
>I'm having problems when trying to JIT IR generated from C++ with clang.
>My code resides in a dynamically loaded shared object, and crashes when I
>call getPointerToFunction, claiming that it encountered a pseudo
>instruction. Interestingly, a very similar code that run as a separate
>executable JITing the same IR works fine. Note that I have not have
>modified LLVM. Any suggestions what could cause this behavior?
>
>Eran.
>
>

Hi Eran,
> For anyone encountering this problem in the future, the cause of this
> problem was debugging symbols (-g) given to clang when generating IR.
glad to hear you got it sorted out.  If you had mentioned exactly which
pseudo instructions were appearing maybe it would have been obvious to
someone what the problem was - just a suggestion to be more explicit next
time you hit a problem!

Ciao, Duncan.

PS: I think debug info is supposed to work with the JIT, so if this is
still a problem with the 3.1 release then I suggest you open a bug report
about it.
>
> On 20/05/2012 12:21, "Weiss, Eran"<Eran.Weiss at emc.com> 
wrote:
>
>> Hi,
>>
>> I'm having problems when trying to JIT IR generated from C++ with
clang.
>> My code resides in a dynamically loaded shared object, and crashes when
I
>> call getPointerToFunction, claiming that it encountered a pseudo
>> instruction. Interestingly, a very similar code that run as a separate
>> executable JITing the same IR works fine. Note that I have not have
>> modified LLVM. Any suggestions what could cause this behavior?
>>
>> Eran.
>>
>>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev