llvm dev - Feb 2010 - [LLVMdev] __fixunsdfdi and etc with Visual Studio JIT?

Hello
> The bitcode was generated by llvm-gcc v2.6 for Mingw32/x86, which is
> available for download at the llvm site.
> Please let me know, if i should tell more.
Well, the answer is pretty obvious then. These calls are not generated
by JIT. They are already in your bitcode - they are generated by
llvm-gcc. The purpose of these calls were alreade explained by Eli.

You should either link libgcc in, ot provide your own implementation
for these functions.

PS: Note the "reply all" button, this way your reply will be sent to
the mailing list as well.
-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University

Thank you for clarification!
I will try to link in the libgcc library and see if there is any
success with that. Otherwise the own implementation will have to do
then.

Kristaps.


On Tue, Feb 2, 2010 at 6:56 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
> Hello
>
>> The bitcode was generated by llvm-gcc v2.6 for Mingw32/x86, which is
>> available for download at the llvm site.
>> Please let me know, if i should tell more.
> Well, the answer is pretty obvious then. These calls are not generated
> by JIT. They are already in your bitcode - they are generated by
> llvm-gcc. The purpose of these calls were alreade explained by Eli.
>
> You should either link libgcc in, ot provide your own implementation
> for these functions.
>
> PS: Note the "reply all" button, this way your reply will be sent
to
> the mailing list as well.
> --
> With best regards, Anton Korobeynikov
> Faculty of Mathematics and Mechanics, Saint Petersburg State University
>

On 2010-02-02 18:56, Anton Korobeynikov wrote:
> Hello
>
>   
>> The bitcode was generated by llvm-gcc v2.6 for Mingw32/x86, which is
>> available for download at the llvm site.
>> Please let me know, if i should tell more.
>>     
> Well, the answer is pretty obvious then. These calls are not generated
> by JIT. They are already in your bitcode - they are generated by
> llvm-gcc.

Some libgcc calls are added by the code generator, for example
I had to provide implementation for these functions (since I disabled
dlsym lookups):
    __divdi3, __udivdi3, __moddi3, __umoddi3, __muldi3, __ashrdi3, 
__ashldi3,  __lshrdi3
and from libc:   memmove, memcpy,     memset

Even if the original bitcode had none of these calls (they were
intrinsics, or just simple divides).

Best regards,
--Edwin