search for: stretpromot

...ertvalue > instead?). Since an sret function will, by definition, have a void > return > type, the new return values will never have to be merged. > > In that light, I will be probably building an internal (i.e., to our > company) > pass that flattens struct return values. stretpromotion was really just for testing. I expect that when MRVs work predictably 100% of the time (even if not something the ABI supports, for example) that the functionality will be pulled into the argpromotion pass. >> Sounds interesting. One thing to keep in mind here is the tradeoff >&...

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

...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 the time (even if not something the ABI > supports, for example) that the functionality will be pulled into the > argpromotion pass. Will sretpromotion still be needed? If the frontends would generate...