Quoting Dave Korn <dave.korn.cyg...@gmail.com>:
Is that documented anywhere? I couldn't find it in the
constraints chapters
of the internals manual.
It's in the reload source code...
And there are subtle register priority implications of having merged or
separate alternatives.
Sorry, is this separate from the thing about appending register constraints
to memory ones or part of it?
It's separate.
Again, no documentation is apparent that
suggests or mentions such a concept as "merged" alternatives.
Well, these things are only really needed to generate good code, and to
generate good code, the way things are now, a port maintainer should
really understand how reload works.
Of course, you can call this a shortcoming of reload and/or the documentation
and/or call the continued need for reload a shortcoming, and propose patches
for any of these issues.
