[PATCH] Deprecate ia64*-*-*

[PATCH] Deprecate ia64*-*-*

[Richard Biener]

ia64 has no maintainer anymore so the following deprecates it
with the goal of eliminating the port for GCC 11 if no maintainer
steps up.

OK?

Thanks,
Richard.

2019-06-13  Richard Biener  <rguenther@suse.de>

	* config.gcc: Mark ia64*-*-* targets as deprecated/obsolete.

Index: gcc/config.gcc
===================================================================
--- gcc/config.gcc	(revision 272239)
+++ gcc/config.gcc	(working copy)
@@ -249,6 +249,7 @@ md_file=
 case ${target} in
   spu*-*-*				\
   | tile*-*-*				\
+  | ia64*-*-*				\
  )
     if test "x$enable_obsolete" != xyes; then
       echo "*** Configuration ${target} is obsolete." >&2

Re: [PATCH] Deprecate ia64*-*-*

[Jeff Law]

On 6/13/19 5:13 AM, Richard Biener wrote:
> 
> ia64 has no maintainer anymore so the following deprecates it
> with the goal of eliminating the port for GCC 11 if no maintainer
> steps up.
> 
> OK?
> 
> Thanks,
> Richard.
> 
> 2019-06-13  Richard Biener  <rguenther@suse.de>
> 
> 	* config.gcc: Mark ia64*-*-* targets as deprecated/obsolete.
Works for me.  James Clarke has been fixing small stuff recently, not
sure if he wants to step into a larger role though.

ia64 has been failing the qsort checking in the scheduler since the day
that checking was introduced -- it shows up building the kernel IIRC.
Nobody's shown any interest in addressing those issues :-)

jeff

Re: [PATCH] Deprecate ia64*-*-*

[Jim Wilson]

On Thu, 2019-06-13 at 09:09 -0600, Jeff Law wrote:
> On 6/13/19 5:13 AM, Richard Biener wrote:
> > 
> > ia64 has no maintainer anymore so the following deprecates it
> > with the goal of eliminating the port for GCC 11 if no maintainer
> > steps up.

OK with me since I'm not the maintainer anymore.

> Works for me.  James Clarke has been fixing small stuff recently, not
> sure if he wants to step into a larger role though.

There are 3 of them.  See
    https://wiki.debian.org/Ports/ia64
It might be useful to send an email to the debian-ia64 list to notify
them.

> ia64 has been failing the qsort checking in the scheduler since the
> day
> that checking was introduced -- it shows up building the kernel IIRC.
> Nobody's shown any interest in addressing those issues :-)

I tried looking at this once.  It looked more difficult than I was
willing to do for IA-64.  There are so many checks in the qsort compare
functions that I don't think you can get a stable sort there.  I think
this is really a sel-sched problem not an IA-64 problem, but the IA-64
port is tied to sel-sched and may not work well without it.  Most other
ports aren't using it by default.

Jim

Re: [PATCH] Deprecate ia64*-*-*

[Joel Sherrill]

Ok with me if no one steps up and the downstream projects like Debian gets
notice. This is just a reflection of this architecture's status in the
world.

--joel

On Thu, Jun 13, 2019, 4:13 AM Richard Biener <rguenther@suse.de> wrote:

>
> ia64 has no maintainer anymore so the following deprecates it
> with the goal of eliminating the port for GCC 11 if no maintainer
> steps up.
>
> OK?
>
> Thanks,
> Richard.
>
> 2019-06-13  Richard Biener  <rguenther@suse.de>
>
>         * config.gcc: Mark ia64*-*-* targets as deprecated/obsolete.
>
> Index: gcc/config.gcc
> ===================================================================
> --- gcc/config.gcc      (revision 272239)
> +++ gcc/config.gcc      (working copy)
> @@ -249,6 +249,7 @@ md_file=
>  case ${target} in
>    spu*-*-*                             \
>    | tile*-*-*                          \
> +  | ia64*-*-*                          \
>   )
>      if test "x$enable_obsolete" != xyes; then
>        echo "*** Configuration ${target} is obsolete." >&2
>

Re: [PATCH] Deprecate ia64*-*-*

[Jim Wilson]

On Thu, Jun 13, 2019 at 10:39 AM Joel Sherrill <joel.sherrill@gmail.com> wrote:
> Ok with me if no one steps up and the downstream projects like Debian gets
> notice. This is just a reflection of this architecture's status in the
> world.

I sent email to the debian-ia64 list half an hour ago.  Just got a
response.  They mentioned that there is also a gentoo group that I
didn't know about, and want to know why exactly we want to deprecate
it.  I can discuss it with them.

Jim

Re: [PATCH] Deprecate ia64*-*-*

[Richard Biener]

On Thu, 13 Jun 2019, Jim Wilson wrote:

> On Thu, Jun 13, 2019 at 10:39 AM Joel Sherrill <joel.sherrill@gmail.com> wrote:
> > Ok with me if no one steps up and the downstream projects like Debian gets
> > notice. This is just a reflection of this architecture's status in the
> > world.
> 
> I sent email to the debian-ia64 list half an hour ago.  Just got a
> response.  They mentioned that there is also a gentoo group that I
> didn't know about, and want to know why exactly we want to deprecate
> it.  I can discuss it with them.

The deprecation reason is a formal one - we do not have a listed
maintainer for the port which is a requirement for port acceptance
and IMHO should be a requirement for it to stay (not sure if that's
written anywhere).  Note GCC 10 will still have the ia64 port it
is just that GCC 11 may not in case nobody steps up as maintainer.

In some way it is also documenting to possible users that their
(target specific) bugs may receive no attention.

Richard.

Re: [PATCH] Deprecate ia64*-*-*

[Jeff Law]

On 6/14/19 1:14 AM, Richard Biener wrote:
> On Thu, 13 Jun 2019, Jim Wilson wrote:
> 
>> On Thu, Jun 13, 2019 at 10:39 AM Joel Sherrill <joel.sherrill@gmail.com> wrote:
>>> Ok with me if no one steps up and the downstream projects like Debian gets
>>> notice. This is just a reflection of this architecture's status in the
>>> world.
>>
>> I sent email to the debian-ia64 list half an hour ago.  Just got a
>> response.  They mentioned that there is also a gentoo group that I
>> didn't know about, and want to know why exactly we want to deprecate
>> it.  I can discuss it with them.
> 
> The deprecation reason is a formal one - we do not have a listed
> maintainer for the port which is a requirement for port acceptance
> and IMHO should be a requirement for it to stay (not sure if that's
> written anywhere).  Note GCC 10 will still have the ia64 port it
> is just that GCC 11 may not in case nobody steps up as maintainer.
> 
> In some way it is also documenting to possible users that their
> (target specific) bugs may receive no attention.
Right.  One could claim many other targets should be reviewed for
possible deprecation.

Jeff

Re: [PATCH] Deprecate ia64*-*-*

[Jason Duerstock]

I volunteer to be maintainer for ia64.

Jason

Re: [PATCH] Deprecate ia64*-*-*

[Jakub Jermář]

Hi Richard!

On 6/13/19 1:13 PM, Richard Biener wrote:
> 
> ia64 has no maintainer anymore so the following deprecates it
> with the goal of eliminating the port for GCC 11 if no maintainer
> steps up.
> 
> OK?

The HelenOS microkernel project would be affected by this as we are
actively developing and maintaining our ia64 port using GCC. Currently
we are using GCC 8.2 but will eventually want to upgrade to newer
versions of GCC, preferably on all our architectures at once and to the
same GCC version.

We build with -O3 and in the past we reported and helped to test fixes
for the following GCC ia64-related bugs:

- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53975
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66660

We are ready to submit and help with more reports like these, it's just
currently we are not bugged by any ia64-related GCC issues.

It would be a tremendous loss if GCC dropped support for ia64 in the
future. Hopefully someone with the right combination of skills will
volunteer.

Jakub

> 
> Thanks,
> Richard.
> 
> 2019-06-13  Richard Biener  <rguenther@suse.de>
> 
> 	* config.gcc: Mark ia64*-*-* targets as deprecated/obsolete.
> 
> Index: gcc/config.gcc
> ===================================================================
> --- gcc/config.gcc	(revision 272239)
> +++ gcc/config.gcc	(working copy)
> @@ -249,6 +249,7 @@ md_file=
>  case ${target} in
>    spu*-*-*				\
>    | tile*-*-*				\
> +  | ia64*-*-*				\
>   )
>      if test "x$enable_obsolete" != xyes; then
>        echo "*** Configuration ${target} is obsolete." >&2
> 

Re: [PATCH] Deprecate ia64*-*-*

[Thomas Schwinge]

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hi!

On Fri, 14 Jun 2019 20:26:58 -0400, Jason Duerstock <jason.duerstock@gmail.com> wrote:
> I volunteer to be maintainer for ia64.

Great!

I see you've already left behind some traces in GCC, and generally the
GNU toolchain, but just to be sure: the procedure then roughly is for you
to display some level of commitment, for example by taking ownership and
resolving reported issues (GCC PRs, for example).  Given there isn't a
IA64 maintainer listed, you'll have to bug the Global Reviewers for
getting your patches approved, and if you do that often/regularly enough,
they'll probably at some point get tired of being the "man in the
middle".  And/or the former maintainer (Jim Wilson) can vouch for you.

I don't see you listed in the FSF 'copyright.list', so that'll need to
get resolved, too; <https://gcc.gnu.org/contribute.html>.


Grüße
 Thomas


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

Re: [PATCH] Deprecate ia64*-*-*

[Jonathan Wakely]

On Sun, 16 Jun 2019 at 14:32, Jakub Jermář wrote:
>
> Hi Richard!
>
> On 6/13/19 1:13 PM, Richard Biener wrote:
> >
> > ia64 has no maintainer anymore so the following deprecates it
> > with the goal of eliminating the port for GCC 11 if no maintainer
> > steps up.
> >
> > OK?
>
> The HelenOS microkernel project would be affected by this as we are
> actively developing and maintaining our ia64 port using GCC. Currently
> we are using GCC 8.2 but will eventually want to upgrade to newer
> versions of GCC, preferably on all our architectures at once and to the
> same GCC version.
>
> We build with -O3 and in the past we reported and helped to test fixes
> for the following GCC ia64-related bugs:
>
> - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53975
> - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66660
>
> We are ready to submit and help with more reports like these, it's just
> currently we are not bugged by any ia64-related GCC issues.

Without feedback we have no way to know if the port is unused and
broken, or just working fine for its users.

One of the best ways you can help is to run the tests and submit
reports to the gcc-testresults mailing list, so that IA64 results are
visible at https://gcc.gnu.org/ml/gcc-testresults/current

You can do that by running "make check -k" (with a suitable -j option)
and then in the build directory running the contrib/test_summary
script (in the GCC sources).

e.g.

make check -k -j8
$gccsrc/contrib/test_summary -m gcc-testresults@gcc.gnu.org | sh

Re: [PATCH] Deprecate ia64*-*-*

[Jeff Law]

On 6/14/19 6:26 PM, Jason Duerstock wrote:
> I volunteer to be maintainer for ia64.
So the first step would be to start your assignment paperwork with the
FSF.  Without it we can't accept non-trivial contributions/fixes from you.

Contact assign@gnu.org to get a past and future copyright assignment for
GCC.  Depending on your precise situation you may also need an employer
disclaimer.

The second step (and you might want to work with Jakub Jermar) would be
to set up a bootstrap & regression test bot of some kind that posts its
results to gcc-testresults@gcc.gnu.org.    We realize ia64 hardware can
be slow, so we certainly will be understanding if results aren't posted
as regularly as other platforms.   But they're still helpful.

Finally, starting to work through some of the existing target specific
issues would be helpful.  I'm sure there's some in BZ and we know
there's some significant problems with how the ia64 port interacts with
the scheduler and the qsort checking (which ultimately prevent linux
kernels from building).

I'm sure folks here are willing to help as you get familiar with the
codebase and start to look at issues.

Jeff