search for: handleaggregateshadowargu

Displaying 4 results from an estimated 4 matches for "handleaggregateshadowargu".

2008 Mar 26
3
[LLVMdev] Wrong calling convention?
Take a look at llvm-gcc. Look for HandleAggregateShadowArgument. Evan On Mar 26, 2008, at 10:31 AM, Óscar Fuentes wrote: > Óscar Fuentes <ofv at wanadoo.es> writes: > >> BTW, -fpcc-struct-return solves the case that motivated this thread. > > -fpcc-struct-return is an ABI change, hence it requires "compiling the > world&qu...
2008 Mar 26
0
[LLVMdev] Wrong calling convention?
Evan Cheng <evan.cheng at apple.com> writes: >> I'll be interested on hearing ideas about how to determine how a >> function returns a small struct, without knowing the internals of the >> struct. > Take a look at llvm-gcc. Look for HandleAggregateShadowArgument. This does not qualify as "without knowing the internals of the struct" :-) DefaultABI::HandleReturnType made an interesting reading, although it uses information which is unaccessible to my compiler. -- Oscar
2008 Mar 26
0
[LLVMdev] Wrong calling convention?
Óscar Fuentes <ofv at wanadoo.es> writes: > BTW, -fpcc-struct-return solves the case that motivated this thread. -fpcc-struct-return is an ABI change, hence it requires "compiling the world". Not acceptable. I'll be interested on hearing ideas about how to determine how a function returns a small struct, without knowing the internals of the struct. -- Oscar
2008 Mar 26
4
[LLVMdev] Wrong calling convention?
Duncan Sands <baldrick at free.fr> writes: >> But you put me on the right track. The problem is that the class is >> returned on the stack. Correction: The class is returned on the FP stack: >> 0x6e08b5b5 <_ZN3Foo6GetFooEv+17>: fldl -0x8(%ebp) >> 0x6e08b5b8 <_ZN3Foo6GetFooEv+20>: leave >> 0x6e08b5b9 <_ZN3Foo6GetFooEv+21>: