search for: printd

...5 António Saragga Seabra <antseabra at gmail.com>: >> > Hi >> > >> > Thank you for your help! Followed your suggestion closely and changed >> > the >> > tutorial library function >> > >> > extern "C" >> > double printd(double X) { >> >   printf("%f\n", X); >> >   return 0; >> > } >> > into >> > >> > >> > export "C" { >> > >> >  void printd(double X) { printf("%f\n", X);return 0;} >> > >> &...

Hi, That seems really simple... just changing the function pointer. But how to do it for the 'printd' function in the Kaleidoscope example? An example how to do this would be super-great. Any help will be much appreciated. Thanks! On Sat, Oct 9, 2010 at 3:55 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > 2010/10/9 António Saragga Seabra <antseabra at gmail.com>: >...

Hi Dmitri, You're right. The lli code should be cleaned up. As David said, there was a time when the call to invalidate the instruction cache was necessary. It isn't necessary anymore. -Andy -----Original Message----- From: Dmitri Rubinstein [mailto:dmitri.rubinstein at googlemail.com] Sent: Tuesday, June 04, 2013 7:20 AM To: David Tweed Cc: Kaylor, Andrew; LLVM Dev Subject: Re:

Hi Buit the Kaleidoscope example under MinGW and everything runs fine except when I try the following example in Chapter 6: extern printd(x); printd(123); where printd is the library function defined in C as extern "C" double printd(double X) { printf("%f\n", X); return 0; } The error message is: LLVM ERROR: Program used external function 'printd' which could not be resolved! Any he...

2010/10/3 Anton Korobeynikov <anton at korobeynikov.info>: >> LLVM ERROR: Program used external function 'printd' which could not be >> resolved! >> Any help will be much appreciated. Thanks! > Windows does not support dynamic linking. You will need to resolve > externals by hand. Why would it not support dynamic linking?  What about loadlibrary and its kin are not sufficient to handle...

On Mon, Oct 4, 2010 at 3:22 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>>> Any help will be much appreciated. Thanks! >>> Windows does not support dynamic linking. You will need to resolve >>> externals by hand. >> >> Why would it not support dynamic linking?  What about loadlibrary and >> its kin are not sufficient to handle

>>> Any help will be much appreciated. Thanks! >> Windows does not support dynamic linking. You will need to resolve >> externals by hand. > > Why would it not support dynamic linking?  What about loadlibrary and > its kin are not sufficient to handle this? Well, you cannot easily export stuff from an executable and this is the main issue here. (And you cannot e.g.