On 11/09/2015 12:38 PM, Bernd Schmidt wrote:
On 11/09/2015 07:52 PM, Trevor Saunders wrote:
yeah, that's more or less my thought, and this makes hookization easier
since you can now mechanically add a hook for each thing in defaults.h
that invokes the macro. Then for each target you can go through and
replace the macro with an override of the hooks. That ends up with the
macros replaced by hooks without writing a lot of patches that need to
go through config-list.mk, and testing on multiple targets which imho is
a giant pain, and rather slow.
We might want to think about making a policy decision to try waiving
some of the testing requirements for target macro -> hook conversions.
Maybe try only a "build to cc1" requirement and see whether that causes
too much breakage.
A config-list.mk build is a build to cc1*, f951, gnat1, so we're not
requiring deep tests on the affected targets. Not sure how much we're
getting by forcing a bootstrap & regression test of that kind of change.
I'm certainly open to this kind of relaxed testing to help this stuff
move forward an complete before we're all retired :-)
Jeff
