Displaying 5 results from an estimated 5 matches for "moduleopt".
Did you mean:
moduleops
2013 Jun 05
2
[LLVMdev] klee linker problem
...6 0x00002ac2ce55eb8b abort + 379
5 libc.so.6 0x00002ac2ce5540ee
6 libc.so.6 0x00002ac2ce554192
7 klee 0x00002ac2cc78779d klee::linkWithLibrary(llvm::Module*,
std::string const&) + 253
8 klee 0x00002ac2cc783954
klee::KModule::prepare(klee::Interpreter::ModuleOptions const&,
klee::InterpreterHandler*) + 2180
9 klee 0x00002ac2cc73715d
klee::Executor::setModule(llvm::Module*, klee::Interpreter::ModuleOptions
const&) + 157
10 klee 0x00002ac2cc71a94a main + 3546
11 libc.so.6 0x00002ac2ce54676d __libc_start_main + 237
12 klee...
2007 Apr 04
1
Issue with pam_winbind for MS AD authentication and moduleoptions
...=tdstelecom.com@lists.samba.org
> [mailto:samba-bounces+noal.miles=tdstelecom.com@lists.samba.org] On
> Behalf Of Andre Fernando Goldacker
> Sent: Wednesday, April 04, 2007 8:40 AM
> To: samba@lists.samba.org
> Subject: [Samba] Issue with pam_winbind for MS AD authentication and
> moduleoptions
>
>
> Hello!
>
> I've configured samba with winbind and pam_winbind module to
> authenticate users that connect to my linux box against MS AD.
>
> Works like a charm. If a user exists both in AD and locally, login
> should assume local users. Again, it works prett...
2013 Jun 06
0
[LLVMdev] klee linker problem
...rt + 379
> 5 libc.so.6 0x00002ac2ce5540ee
> 6 libc.so.6 0x00002ac2ce554192
> 7 klee 0x00002ac2cc78779d klee::linkWithLibrary(llvm::Module*,
> std::string const&) + 253
> 8 klee 0x00002ac2cc783954
> klee::KModule::prepare(klee::Interpreter::ModuleOptions const&,
> klee::InterpreterHandler*) + 2180
> 9 klee 0x00002ac2cc73715d
> klee::Executor::setModule(llvm::Module*, klee::Interpreter::ModuleOptions
> const&) + 157
> 10 klee 0x00002ac2cc71a94a main + 3546
> 11 libc.so.6 0x00002ac2ce54676d _...
2003 Nov 16
0
[LLVMdev] Packages
...concatenated into one big "source
description" segment. I don't see much utility in that myself. If by
merged you mean that commonly named global symbols are reduced to a
single copy (like linkonce), then this defeats the point. What if a
compiler wanted to emit a variable named "ModuleOptions" in each
translation unit that describes the _source_ compiler options used to
compile the module. If those all get merged away, you lose the ability
to distinguish different "ModuleOptions" for different modules. This is
the reason for point #6.
>
> > 6. There ar...
2003 Nov 16
3
[LLVMdev] Packages
> The point here is that XPL needs to keep track of what a given variable
> represents at the source level. If the compiler sees a map that is
> initially small it might represent it in LLVM assembly as a vector of
> pairs. Later on, it gets optimized into being a hash table. In order to
> do that and keep track of things, I need to know that the vector of
> pairs is