Migrate to i?86-pc-windows triplet from i?86-pc-mingw32?

["Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>]

Christopher Faylor wrote:

> On Sat, Oct 30, 2004 at 06:15:20PM -0500, Aaron W. LaFramboise wrote:
> 
>>I think the real trouble here is the name, MinGW.  I think its just a
>>historical relic of the port, which came from Cygwin, which wasn't
>>"MinGW."  I would be very tremendously happy if we could just start
>>calling it i686-pc-windows, or *-win32, or whatever, if only so my
>>collegues would understand that the Windows target can be as first-order
>>as the other targets.  Besides, theres no *-MinGSolaris or *-MinGARM.
> 
> I agree that this should be just called i?86-*-windows.  It would take
> some effort to progate this throughout the gcc, binutils, and gdb
> toolchains, though.

I think the roadmap would go like this:

-Clean up config.sub.  Currently, -windows, -windowsnt, and -winnt are
recognized.  These should probably be merged.

-Ensure mingwrt handles -windows correctly.

-Update binutils */config.* and testsuite to make -windows equivilent to
-mingw32.

-Update GCC's config.gcc and testsuite to make -windows equivilent to
-mingw32.

-Check if GDB needs any updating.  As far as I know, an official FSF gdb
release has never supported -mingw32.

-When the timing seems right, somehow change config.guess.  Since
changing from -mingw32 to -windows seems likely to break a lot of
configures, it seems like a good thing not to mess that up for existing
configurations.  Perhaps config.guess would only report i686-pc-windows
if uname actually reports Windows rather than MinGW (presently, none of
the popular Windows unames do this).  At some time in the future, either
MinGW's uname or config.guess might be changed so that i686-pc-mingw32
is never reported, but thats probably a long way off.

Would it be OK with you if I started this process?

Aaron W. LaFramboise