This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: FX <fxcoudert at gmail dot com>
To: GCC Development <gcc at gcc dot gnu dot org>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 20 Aug 2015 23:06:06 +0200
Subject: Should we remove remnants of UWIN support in gcc/config.* files?
Authentication-results: sourceware.org; auth=none

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 be removed:

powerpc-*-beos
i370-*-opened* | i370-*-mvs*
i386-*-vsta
i[34567]86-*-udk*
i[34567]86-*-sysv4*
i[34567]86-sequent-ptx4* | i[34567]86-sequent-sysv4*
i[34567]86-*-sco3.2v5*

Is there a good reason for not removing those targets? If not, Iâll try to track them down, check that they are indeed unsupported, and propose a patch removing them.

Attachment: uwin.ChangeLog
Description: Binary data

Attachment: uwin.diff
Description: Binary data

Follow-Ups:
- Re: Should we remove remnants of UWIN support in gcc/config.* files?
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]