Displaying 3 results from an estimated 3 matches for "completionproc".
2013 Jan 20
2
[LLVMdev] Clang's approach to anonymous struct pointer parameters
For the following code:
struct XBeePacket;
typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2);
struct
XBeePacket
{
bool mField1;
CompletionProc mCompletionProc;
};
Why does clang emit this IR?
%struct.XBeePacket = type { i8, {}* }
define void
@MyCompletionProc(%struct.XBeePacket* %inPa...
2013 Jan 20
0
[LLVMdev] Clang's approach to anonymous struct pointer parameters
Hi Rick,
this is a bug in Clang's LLVM-IR code generator:
http://llvm.org/bugs/show_bug.cgi?id=14920
Best,
Florian
On Sunday, January 20, 2013 01:57:37 Rick Mann wrote:
> For the following code:
>
> struct XBeePacket;
>
> typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2);
>
> struct
> XBeePacket
> {
> bool mField1;
> CompletionProc mCompletionProc;
> };
>
> Why does clang emit this IR?
>
> %struct.XBeePacket = type { i8, {}* }
>
>...
2013 Jan 24
2
[LLVMdev] What would cause instructions to NOT make it into the module?
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Sean Silva
> Subject: Re: [LLVMdev] What would cause instructions to NOT make it into the module?
> It is a pass that can be run like any other pass. See createVerifierPass().
You can also just call verifyModule() with the appropriate parameters; it's defined in