Displaying 7 results from an estimated 7 matches for "lt_module".
2004 Dec 05
0
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
...l.c, it doesn't build cleanly with VC++:
\llvm\lib\System\ltdl.c(972) : warning C4090: 'function' : different 'const' qualifiers
\llvm\lib\System\ltdl.c(1332) : warning C4090: '=' : different 'const' qualifiers
\llvm\lib\System\ltdl.c(1431) : warning C4113: 'lt_module (__cdecl *)()' differs in parameter lists from 'lt_module_open (__cdecl *)'
\llvm\lib\System\ltdl.c(1431) : warning C4113: 'int (__cdecl *)()' differs in parameter lists from 'lt_module_close (__cdecl *)'
\llvm\lib\System\ltdl.c(1431) : warning C4113: 'void *(__cdecl...
2004 Dec 28
1
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
...build cleanly with VC++:
>
> \llvm\lib\System\ltdl.c(972) : warning C4090: 'function' : different 'const' qualifiers
> \llvm\lib\System\ltdl.c(1332) : warning C4090: '=' : different 'const' qualifiers
> \llvm\lib\System\ltdl.c(1431) : warning C4113: 'lt_module (__cdecl *)()' differs in parameter lists from 'lt_module_open (__cdecl *)'
> \llvm\lib\System\ltdl.c(1431) : warning C4113: 'int (__cdecl *)()' differs in parameter lists from 'lt_module_close (__cdecl *)'
> \llvm\lib\System\ltdl.c(1431) : warning C4113: 'void...
2004 Dec 04
3
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
ltdl.h fully supports windows platforms (lots of them). That isn't the
issue. The issue is setting up the #defines to reflect the windows
system. e.g. HAVE_DLOPEN needs to be false
Reid.
On Fri, 2004-12-03 at 20:35, Chris Lattner wrote:
> On Fri, 3 Dec 2004, Jeff Cohen wrote:
>
> > It will have to be Morten. I can't get ltdl.c to compile. But wasn't
> > the
2007 Jul 20
2
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
...lso appears to have the same behaviour as its non-lt_
counterpart, so you'd think you'd have to do the same as above; use
lt_dlerror().
However, it appears things like libtool's
static lt_ptr
sys_dl_sym (loader_data, module, symbol)
lt_user_data loader_data;
lt_module module;
const char *symbol;
{
lt_ptr address = dlsym (module, symbol);
if (!address)
{
LT_DLMUTEX_SETERROR (DLERROR (SYMBOL_NOT_FOUND));
}
return address;
}
break the ability to detect an undefined symbol versus a symbol with a
value o...
2007 Jul 20
0
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
...non-lt_
> counterpart, so you'd think you'd have to do the same as above; use
> lt_dlerror().
>
> However, it appears things like libtool's
>
> static lt_ptr
> sys_dl_sym (loader_data, module, symbol)
> lt_user_data loader_data;
> lt_module module;
> const char *symbol;
> {
> lt_ptr address = dlsym (module, symbol);
>
> if (!address)
> {
> LT_DLMUTEX_SETERROR (DLERROR (SYMBOL_NOT_FOUND));
> }
>
> return address;
> }
>
> break the abi...
2007 Jul 20
0
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
Hi Ralph,
On Fri, 2007-07-20 at 10:38 +0100, Ralph Corderoy wrote:
> Hi Chris,
> I could be missing something, but shouldn't the use of dlsym() be
>
> char *err;
> void *p;
>
> if ((err = dlerror())) {
> error("earlier undetected dlerror: %s\n", err);
> }
> p = dlsym(handle, sym);
> if ((err = dlerror())) {
>
2007 Jul 20
4
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
Hi Chris,
> Once you have that, you are hitting another problem. Specifically,
> the JIT::getPointerToNamedFunction method in
> lib/ExecutionEngine/JIT/Intercept.cpp just does a dlsym on missing
> symbols. If dlsym returns null, you get the error message.
>
> The problem here is that .objc_class_name_* are special symbols that
> are used by the objc linker support and they