Displaying 4 results from an estimated 4 matches for "addr_045442a0".
2008 Mar 26
2
[LLVMdev] Wrong calling convention?
...ceives a wrong
result or the application ends on what it seems a corrupt stack.
The function is a C++ static method that returns a class with just a
`double' data member:
class Foo {
double data;
};
My compiler abstracts this as a [8 x i8] array. This is the llvm code:
define internal i1 @Addr_045442A0() {
alloca [8 x i8], align 4 ; <[8 x i8]*>:1 [#uses=2]
alloca i1, align 4 ; <i1*>:2 [#uses=2]
tail call void @F95478DA5_FFI_FN( [8 x i8]* %1 sret )
bitcast [8 x i8]* %1 to i8* ; <i8*>:3 [#uses=1]
tail call void @Addr_004DDA18( i8* inttoptr (i32 14545104 to i8*), i8* %3 )...
2008 Mar 26
0
[LLVMdev] Wrong calling convention?
Hi,
> define internal i1 @Addr_045442A0() {
> alloca [8 x i8], align 4 ; <[8 x i8]*>:1 [#uses=2]
> alloca i1, align 4 ; <i1*>:2 [#uses=2]
> tail call void @F95478DA5_FFI_FN( [8 x i8]* %1 sret )
this call uses the "struct-return" convention (due to the sret attribute).
On x86 this means that the calle...
2008 Mar 26
4
[LLVMdev] Wrong calling convention?
Hi Duncan.
Duncan Sands <baldrick at free.fr> writes:
>> define internal i1 @Addr_045442A0() {
>> alloca [8 x i8], align 4 ; <[8 x i8]*>:1 [#uses=2]
>> alloca i1, align 4 ; <i1*>:2 [#uses=2]
>> tail call void @F95478DA5_FFI_FN( [8 x i8]* %1 sret )
>
> this call uses the "struct-return" convention (due to the sret attribute).
> On x86...
2008 Mar 26
0
[LLVMdev] Wrong calling convention?
Hi Óscar,
> >> define internal i1 @Addr_045442A0() {
> >> alloca [8 x i8], align 4 ; <[8 x i8]*>:1 [#uses=2]
> >> alloca i1, align 4 ; <i1*>:2 [#uses=2]
> >> tail call void @F95478DA5_FFI_FN( [8 x i8]* %1 sret )
> >
> > this call uses the "struct-return" convention (due to the sre...