Displaying 3 results from an estimated 3 matches for "ctor1".
Did you mean:
ctor
2008 Jan 26
0
[LLVMdev] Test Results
On Jan 25, 2008, at 9:35 PM, Bill Wendling wrote:
> Sorry, I forgot to mention. It's a PPC PowerBook G4 running Mac OS X
> 10.4.11.
>
> -bw
OK, ppc32 EH used to work better than this (although I haven't tried
it on 10.4). I'll have a look.
> On Jan 25, 2008, at 6:14 PM, Dale Johannesen wrote:
>
>> What target?
>>
>> On Jan 25, 2008, at 6:06 PM,
2008 Jan 26
3
[LLVMdev] Test Results
Sorry, I forgot to mention. It's a PPC PowerBook G4 running Mac OS X
10.4.11.
-bw
On Jan 25, 2008, at 6:14 PM, Dale Johannesen wrote:
> What target?
>
> On Jan 25, 2008, at 6:06 PM, Bill Wendling wrote:
>
>> Here are my test results for the 2.2 prerelease.
>>
>> Built objDir == srcDir, release, and with the pre-built LLVM-GCC
>> binary.
>>
2020 Jan 26
2
[RFC] Replacing inalloca with llvm.call.setup and preallocated
...assuming each argument has a constructor that may throw:
```llvm
%cs = call token @llvm.call.setup(i32 3)
%m0 = call i8* @llvm.call.alloc(token %cs, i32 0)
invoke void @ctor0(i8* %m0)
to label %cont0 unwind label %cleanupCall
cont0:
%m1 = call i8* @llvm.call.alloc(token %cs, i32 1)
invoke void @ctor1(i8* %m1)
to label %cont1 unwind label %cleanup0
cont1:
%m2 = call i8* @llvm.call.alloc(token %cs, i32 2)
invoke void @ctor2(i8* %m2)
to label %cont2 unwind label %cleanup1
cont2:
call void @use_callsetup(i8* preallocated %m1,
i32 13,
i8*...