Re: Should we remove remnants of UWIN support in gcc/config.* files?

2015-08-20 Thread Joseph Myers
On Thu, 20 Aug 2015, FX wrote: PS: gcc/config.host and gcc/config.build include some other such targets… without checking them all, I think the following could be removed: powerpc-*-beos i370-*-opened* | i370-*-mvs* i386-*-vsta i[34567]86-*-udk* i[34567]86-*-sysv4*

Should we remove remnants of UWIN support in gcc/config.* files?

2015-08-20 Thread FX
UWIN support was apparently removed from GCC in 2008. Yet some traces can still be found in gcc/config.* files. Attached patch would remove them. OK to commit? FX PS: gcc/config.host and gcc/config.build include some other such targets… without checking them all, I think the following could

Re: Should we remove remnants of UWIN support in gcc/config.* files?

2015-08-20 Thread FX
Well, they aren't *targets*, but *host* and *build* systems. Yes, but do we maintain a list of support host or build systems, that would be different from our list of supported targets? (That’s a question out of curiosity. I do agree with the rest of your message: in practice, they are not

Re: Should we remove remnants of UWIN support in gcc/config.* files?

2015-08-20 Thread Joseph Myers
On Thu, 20 Aug 2015, FX wrote: Well, they aren't *targets*, but *host* and *build* systems. Yes, but do we maintain a list of support host or build systems, that would be different from our list of supported targets? I don't think there's such a list. For any such system that's not a

Re: Should we remove remnants of UWIN support in gcc/config.* files?

2015-08-20 Thread Joel Sherrill
On August 20, 2015 5:22:47 PM EDT, Joseph Myers jos...@codesourcery.com wrote: On Thu, 20 Aug 2015, FX wrote: Well, they aren't *targets*, but *host* and *build* systems. Yes, but do we maintain a list of support host or build systems, that would be different from our list of supported