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.
Bernd
