> This construct bothers me. If it occurred only once, it might not
> bother me so much, but (arch_info->mach != bfd_mach_ppc_e500) appears
> far too often in the code for me to be comfortable with it. Suppose
> we have another core with a similar property (of passing everything
> in GPRs). If this happens, we'll end up with a proliferation of
> additional checks for all of these different cores and things will
> become quite unreadable. Please introduce a predicate into which
> we can put this test and perhaps others as they arise. Then, only
> the predicate will need to be modified.