Displaying 4 results from an estimated 4 matches for "bycopi".
Did you mean:
bycopy
2013 May 27
0
[LLVMdev] RFC: Converting byref captures into bycopy
Hi all,
I have been looking at how to convert by-reference captures into by-copy captures for captured statements and possibly C++ lambdas, and am looking for some feedback on my approach. The motivation for trying to use copy captures is to avoid unnecessary loads that are otherwise required inside the outlined function. This can be important when the outlined function represents the body of a
2007 Jun 26
0
[LLVMdev] comments on Bug 1521 (Revamp LLVM by-value structure passing)
Hi Rafael,
> 2) add a "byref" mark in the pointer argument.
I think you mean "bycopy" or "byval" here.
> 3) Have llvm-gcc create a copy before calling the function.
Don't forget that the function may be called by code that
was not compiled by LLVM. That's why we have to pay attention
to the ABI! Solution (3) supposes we have control over both
2007 Jun 26
1
[LLVMdev] comments on Bug 1521 (Revamp LLVM by-value structure passing)
> > 2) add a "byref" mark in the pointer argument.
>
> I think you mean "bycopy" or "byval" here.
Yes, good catch.
> > 3) Have llvm-gcc create a copy before calling the function.
>
> Don't forget that the function may be called by code that
> was not compiled by LLVM. That's why we have to pay attention
> to the ABI! Solution
2007 Jun 26
3
[LLVMdev] comments on Bug 1521 (Revamp LLVM by-value structure passing)
This is my current understanding of the current situation and the
proposed solution.
Currently llvm-gcc compiles
-----------------------
struct cpp_num
{
unsigned long high;
unsigned long low;
char unsignedp;
};
void g(unsigned long);
void f(struct cpp_num num) {
g(num.high + 1);
}
----------------------
into
---------------------------------------------------------------------------