Pedro Alves wrote:
> How would people prefer something like this going forward? Start with
> extracting common stuff into config/, while making sure e.g, at least
> one of mingw or cygwin still bootstraps/tests OK; or, start by
> updating config/arm/ with copies of what's under config/i386/, and once
> that is in, work on extracting/abstracting common stuff out?
I think it would be better to do the commoning out first, having cygwin and
mingw to test that it's correct with, and then extend the arm stuff to make
use of it; it save what would be the otherwise redundant effort of adding a
bunch of files only to take them away again.
> Vincent pointed out the obvious abuses that are 100% reusable, but,
> I'd like to reuse e.g., config/i386/winnt.c, config/i386/winnt-cxx.c,
> config/i386/winnt-stubs.c for ARM as well. E.g, currently, I've copied
> config/i386/winnt.c over the current config/arm/pe.c (completelly replacing
> it), and adjusted it a bit to make it work for ARM. As you can see from
> the hunk below, the main juice is shareable here (there's no fastcall
> on ARM WinCE):
I see in general no limits on what we should common out, anything that is
truly target-independent and can be useful elsewhere is fair game. I suggest
that on doing so we rename files and functions to use a "pe-" or "pe_" prefix,
replacing any current "ix86_" or "arm_" or whatever else.
cheers,
DaveK
