This is the mail archive of the
mailing list for the GCC project.
Re: Deprecate SH5/SH64
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Oleg Endo <oleg dot endo at t-online dot de>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>, Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>
- Date: Tue, 18 Aug 2015 13:11:46 -0400
- Subject: Re: Deprecate SH5/SH64
- Authentication-results: sourceware.org; auth=none
- References: <DB2C9AFC-A5C6-4540-B503-E6449B1B79E2 at t-online dot de>
On Tue, Aug 18, 2015 at 1:00 PM, Oleg Endo <firstname.lastname@example.org> wrote:
> Hi all,
> Kaz and I have been discussing the SH5/SH64 status, which is part of the SH port, every now and then. To our knowledge, there is no real hardware available as of today and we don't think there are any real users for a SH5/SH64 toolchain out there. Moreover, the SH5/SH64 parts of the SH port haven't been touched by anybody for a long time. The only exception is occasional ad-hoc fixes for bug reports from people who build GCC for every architecture that is listed in the Linux kernel. However, we don't actually know whether code compiled for SH5/SH64 still runs at an acceptable level since nobody has been doing any testing for that architecture for a while now.
> If there are no objections, we would like to deprecate SH5/SH64 support as of GCC 6.
> Initially this would include an announcement on the changes page and the removal of any documentation related to SH5/SH64. After GCC 6 we might start removing configure options and the respective code paths in the target.