Displaying 4 results from an estimated 4 matches for "returns_multipl".
Did you mean:
returns_multiple
2008 Jun 02
2
[LLVMdev] Plans considering first class structs and multiple return values
...l be
impossible to distinguish between a function returning a single struct and a
function returning multiple values.
I'm not sure this is a big problem, but it makes adding a return value to a
function harder. I'm not sure this is really a problem though. Would adding a
function attribute returns_multiple or something like that be useful?
returns_multiple would mean to interpret the returned struct as multiple
return values and in particular forbids to use the resulting value in any way
but as an operand to extractvalue. The main goal of this is to make
adding/removing an argument easier, because y...
2008 May 30
0
[LLVMdev] Plans considering first class structs and multiple return values
On May 30, 2008, at 9:11 AM, Matthijs Kooijman wrote:
> Hi all,
>
> I've been implementing some stuff that uses the new structs-as-
> firstclass
> values code. Apart from some implementation problems, I'm spotting a
> few
> structural problems that seem non-trivial to fix.
Hi, thanks for your interest!
> Furthermore, as far as I've understood, the
2008 Jun 02
0
[LLVMdev] Plans considering first class structs and multiple return values
...tion returning a single
> struct and a
> function returning multiple values.
>
> I'm not sure this is a big problem, but it makes adding a return
> value to a
> function harder. I'm not sure this is really a problem though. Would
> adding a
> function attribute returns_multiple or something like that be useful?
> returns_multiple would mean to interpret the returned struct as
> multiple
> return values and in particular forbids to use the resulting value
> in any way
> but as an operand to extractvalue. The main goal of this is to make
> adding/remo...
2008 May 30
3
[LLVMdev] Plans considering first class structs and multiple return values
Hi all,
I've been implementing some stuff that uses the new structs-as-firstclass
values code. Apart from some implementation problems, I'm spotting a few
structural problems that seem non-trivial to fix.
In particular, now that structs are a first class values, the old way or
returning multiple values is a bit confusing. The old way had a variable
number of arguments to the return