Displaying 3 results from an estimated 3 matches for "createbuildmrv".
2008 Jun 07
0
[LLVMdev] Plans considering first class structs and multiple return values
...t;> later if we find it would be of significant use or convenience.
> By then, we will probably have though our backend to read
> insertvalue chains,
> so it won't be really necessary anymore :-) But let's keep it in mind.
If you're using IRBuilder, why not just add a new CreateBuildMRV
method that inserts the sequence of insertvalue's for you?
> Reconsidering, the sretpromotion pass might not be the best place
> for this. It
> currently promotes the special sret pointer arguments to multiple
> return
> values (I should probably modify it to use a struct...
2008 Jun 02
2
[LLVMdev] Plans considering first class structs and multiple return values
Hi Dan,
> The requirement to update all callers' call instructions when a callee
> gets a new return value is also present in the current MRV-mechanism
> with getresult. It's not been a problem we've worried about so far.
I didn't mean you can get away without updating your calllers, I'm just saying
it could be a bit easier.
> Can you give some background about
2008 Jun 09
3
[LLVMdev] Plans considering first class structs and multiple return values
...returning a single value stand out even more,
since a function returning 0 or more than 1 values will always return a
struct, while a function returning 1 value will just return that value. Don't
think this is really a problem, though.
> If you're using IRBuilder, why not just add a new CreateBuildMRV
> method that inserts the sequence of insertvalue's for you?
Hmm, that would actually make sense I guess. I'm not currently using
IRBuilder, but I might move some code into there.
> stretpromotion was really just for testing. I expect that when MRVs
> work predictably 100% of...