From: Jeff Law <law@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Remove tilegx port
Date: Fri, 27 Apr 2018 13:32:17 -0600 [thread overview]
Message-ID: <4d252cf1-e2e6-59cd-5328-f90e28a1a770@redhat.com> (raw)
In-Reply-To: <2DDA84B0-56C7-4B4B-8C23-DEF2001B6BEB@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
On 04/27/2018 11:42 AM, Richard Biener wrote:
> On April 27, 2018 7:26:19 PM GMT+02:00, Jeff Law <law@redhat.com> wrote:
>> On 04/27/2018 09:36 AM, Joseph Myers wrote:
>>> Since tile support has been removed from the Linux kernel for 4.17,
>>> this patch removes the (unmaintained) port to tilegx from glibc (the
>>> tilepro support having been previously removed). This reflects the
>>> general principle that a glibc port needs upstream support for the
>>> architecture in all the components it build-depends on (so binutils,
>>> GCC and the Linux kernel, for the normal case of a port supporting
>> the
>>> Linux kernel but no other OS), in order to be maintainable.
>>>
>>> Apart from removal of sysdeps/tile and sysdeps/unix/sysv/linux/tile
>>> (omitted from the diffs below), there are updates to various comments
>>> referencing tile for which removal of those references seemed
>>> appropriate. The configuration is removed from README and from
>>> build-many-glibcs.py. contrib.texi keeps mention of removed
>>> contributions, but I updated Chris Metcalf's entry to reflect that he
>>> also contributed the non-removed support for the generic Linux kernel
>>> syscall interface. __ASSUME_FADVISE64_64_NO_ALIGN support is
>> removed,
>>> as it was only used by tile.
>> Given tilegx/tilepro removal from the kernel and glibc, should we go
>> ahead and deprecate them in GCC? The only tilegx/tilepro
>> configurations
>> are -linux.
>
> Makes sense to me. Let's deprecate it for GCC 8 and remove from trunk.
>
> Richard.
>
>> Jeff
>
Here's what I committed to the trunk and the release branch. I'll
find/update the appropriate web page momentarily.
jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 708 bytes --]
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 4db67b8d069..f81b09f8739 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2018-04-27 Jeff Law <law@redhat.com>
+
+ * config.gcc: Mark tile* targets as deprecated/obsolete.
+
2018-04-27 Richard Biener <rguenther@suse.de>
* config/aarch64/aarch64.c: Simplify ap.__stack advance and
diff --git a/gcc/config.gcc b/gcc/config.gcc
index e58494c1c17..a5defb0f005 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -237,6 +237,7 @@ md_file=
# Obsolete configurations.
case ${target} in
powerpc*-*-*spe* \
+ | tile*-*-* \
)
if test "x$enable_obsolete" != xyes; then
echo "*** Configuration ${target} is obsolete." >&2
next prev parent reply other threads:[~2018-04-27 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 15:36 Remove tilegx port Joseph Myers
2018-04-27 16:19 ` Adhemerval Zanella
2018-04-27 17:26 ` Jeff Law
2018-04-27 17:42 ` Richard Biener
2018-04-27 19:32 ` Jeff Law [this message]
2021-09-10 11:50 ` Richard Biener via Libc-alpha
2021-09-10 13:53 ` Jeff Law via Libc-alpha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d252cf1-e2e6-59cd-5328-f90e28a1a770@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=richard.guenther@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).