Displaying 3 results from an estimated 3 matches for "outmodule".
Did you mean:
getmodule
2016 Sep 12
2
Counterintuitive use of LLVMBool in C-API?
Hi,
I stumbled across the following:
> /* Builds a module from the bitcode in the specified memory buffer,
> returning a
> reference to the module via the OutModule parameter. Returns 0 on success.
> */
> LLVMBool LLVMParseBitcode2(LLVMMemoryBufferRef MemBuf,
> LLVMModuleRef *OutModule);
However in most scenarios i know, a Bool is something like
0 = False
!0 = True
In short: is it just me or is this really counterintuitive?
-------------- next part...
2016 Sep 12
1
Counterintuitive use of LLVMBool in C-API?
...; On 12 Sep 2016, at 09:59, Alexander Benikowski via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> >
> > I stumbled across the following:
> > /* Builds a module from the bitcode in the specified memory buffer,
> returning a
> > reference to the module via the OutModule parameter. Returns 0 on
> success. */
> > LLVMBool LLVMParseBitcode2(LLVMMemoryBufferRef MemBuf,
> > LLVMModuleRef *OutModule);
> > However in most scenarios i know, a Bool is something like
> > 0 = False
> > !0 = True
> >
> > In short: is it just me or...
2017 Sep 18
0
Counterintuitive use of LLVMBool in C-API?
...59, Alexander Benikowski via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>> >
>> > I stumbled across the following:
>> > /* Builds a module from the bitcode in the specified memory buffer,
>> returning a
>> > reference to the module via the OutModule parameter. Returns 0 on
>> success. */
>> > LLVMBool LLVMParseBitcode2(LLVMMemoryBufferRef MemBuf,
>> > LLVMModuleRef *OutModule);
>> > However in most scenarios i know, a Bool is something like
>> > 0 = False
>> > !0 = True
>> >
>>...