Displaying 3 results from an estimated 3 matches for "llvmresult".
2016 Sep 12
1
Counterintuitive use of LLVMBool in C-API?
Of course, this is normal for C-APIs. But maybe change the name to
LLVMResult to propagate the real use? I am not arguing about the results
themself. They are standard. But the name is missguiding. As long as it's
consistent i know that i have to write an extra record operator in Delphi
to reflect this.
2016-09-12 11:11 GMT+02:00 David Chisnall <David.Chisnall at cl....
2017 Sep 18
0
Counterintuitive use of LLVMBool in C-API?
...his case it is the other way around. 0 means False and anything else
means true :/ (so it acts more like a "traditional" bool)
2016-09-12 11:17 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>:
> Of course, this is normal for C-APIs. But maybe change the name to
> LLVMResult to propagate the real use? I am not arguing about the results
> themself. They are standard. But the name is missguiding. As long as it's
> consistent i know that i have to write an extra record operator in Delphi
> to reflect this.
>
> 2016-09-12 11:11 GMT+02:00 David Chisnall &...
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: