Robin Dapp <rdapp....@gmail.com> writes: > Hi Richard, > > cool, thanks. I just gave it a try with my test cases and it does what > it is supposed to do, at least if I disable the register pressure check :) > A cursory look over the test suite showed no major regressions and just > some overly specific tests. > > My test case only works before split, though, as the UNSPEC predicates will > prevent further combination afterwards. > > Right now the (pre-RA) code combines every instance disregarding the actual > pressure and just checking if the "new" value does not occupy more registers > than the old one. > > - Shouldn't the "pressure" also depend on the number of available hard regs > (i.e. an nregs = 2 is not necessarily worse than nregs = 1 if we have 32 > hard regs in the new class vs 16 in the old one)?
Right, that's what I meant by extending/tweaking the pressure heuristics for your case. > - I assume/hope you expected my (now obsolete) fwprop change could be re-used? Yeah, I was hoping you'd be able to apply similar heuristics to the new pass. (I didn't find time to look at the old heuristics in detail, though, sorry.) I suppose the point of comparison would then be "new pass with current heuristics" vs. "new pass with relaxed heuristics". It'd be a good/interesting test of the new heuristics to apply them without any constraint on the complexity of the SET_SRC. > Otherwise we wouldn't want to unconditionally "propagate" into a loop for > example? > For my test case the combination of the vec_duplicate into all insns leads > to "high" register pressure that we could avoid. > > How should we continue here? I suppose you'll first want to get this version > to the trunk before complicating it further. Yeah, that'd probably be best. I need to split the patch up into a proper submission sequence, do more testing, and make it RFA quality. Jeff has also found a couple of regressions that I need to look at. But the substance probably won't change much, so I don't think you'd be wasting your time if you developed the heuristics based on the current version. I'd be happy to review them on that basis too (though time is short at the moment). Thanks, Richard
