public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Rene Rebe <rene@exactcode.de>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de, frank.scheiner@web.de
Subject: Re: [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets
Date: Wed, 12 Jun 2024 19:44:22 +0100	[thread overview]
Message-ID: <ZmnshjFlP_DzWUyX@zen.kayari.org> (raw)
In-Reply-To: <20240612.123343.1340522057045758230.rene@exactcode.de>

On 12/06/24 12:33 +0200, Rene Rebe wrote:
>Hey there,
>
>I wanted to come back to maintaining the ia64 port as discussed
>preciously the other month on the gcc list.
>
>It has been some days as we were busy releasing the biggest release of
>our Embdded T2/Linux distribution [0] and we obviously did not want to
>propose to enable LRA for IA-64 in the last last days of the gcc 14
>release process.
>
>We used the time to further stability test the LRA enabled GCC built
>in T2/Linux and set up running the GCC testsuite accordingly for which
>Frank posted test results from GCC git for reference [1] and w/ LRA
>[2] enabled with only minimal changes, but also some new testsuite
>passes. Due to the -j4 run I summed up the text files result manually
>in LibreOffice:

But the .sum files already combine all the results into one file.


>gcc
>35572, 31789
>33273, 28492
>37189, 36804
>28735, 37634
>sum 134769, 134719
>
>g++
>69349, 61058
>61467, 63545
>61614, 63752
>56027, 60102
>sum 248457, 248457
>
>gfortran
>18895, 17502
>19329, 19051
>13950, 17583
>17442, 15482
>sum 69616, 69618
>
>objc
>693, 783
>760, 669
>609, 649
>716, 677
>sum 2778, 2778
>
>ibstdc++
>4495, 4635
>4001, 3629
>3958, 4580
>4970, 4580
>sum 17424, 17424
>
>The LRA enabled built Linux kernel and whole user-land packages boot
>and function normally, too.
>
>Instead of looking into random test suite failures, I would first
>rather try to allocate some time to look into some build failures for
>more advanced real-world open source packages that I observered over
>the last years and already occured unrelated of the LRA enablement.
>
>> > On Mar 7, 2024, at 20:08, Richard Biener <rguenther@suse.de> wrote:
>> >> I saw the deprecation of ia64*-*-* scrolling by [1].
>> >>
>> >> Which surprised me, as (minor bugs aside) gcc ia64*-*-linux just works for us and
>> >> we still actively support it as part of our T2 System Development Environment [2].
>> >>
>> >> For ia64 we are currently a team of three and also keep maintaining linux-kernel and
>> >> glibc git trees with ia64 restored and hope to bring back ia64 to linux upstream the
>> >> coming months as promised. [3]
>> >>
>> >> Despite popular believe ia64 actually just works for all those projects and we already
>> >> fixed the few minor bugs we could find or reproduce.
>> >>
>> >> Last week I also already patched and tested enabling LRA for ia64 in gcc [4] and could
>> >> -without any regression- compile a full ia64 T2/Linux release ISO that boots and runs
>> >> including an X desktop and Gtk applications. That was of course even with the latest
>> >> linux kernel and glibc versions with ia64 support restored respectively.
>> >>
>> >> Given there are currently no other volunteers, I therefore with this email step up and
>> >> offer to become ia64 maintainer for GCC to keep the code compiling, tested and
>> >> un-deprecated for the next years and releases to come.
>> >
>> > You’re welcome - we look forward to LRA enablement with ia64 and for it to get an
>> > active maintainer.  Note maintainers are appointed by the Steering Committee.
>
>[0] https://t2sde.org/
>[1] https://gcc.gnu.org/pipermail/gcc-testresults/2024-May/816346.html
>[2] https://gcc.gnu.org/pipermail/gcc-testresults/2024-May/816422.html
>
>-- 
>  René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
>  https://exactcode.com | https://t2sde.org | https://rene.rebe.de


      parent reply	other threads:[~2024-06-12 18:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45833A6D-A84C-4276-AADB-BE2923886F64@exactcode.de>
     [not found] ` <A935D68A-1B29-421A-A239-52CA50ADA239@suse.de>
     [not found]   ` <3DAB006A-ACE2-4BEC-AA01-87625DBEE259@exactcode.de>
2024-06-12 10:33     ` Rene Rebe
2024-06-12 10:42       ` [PATCH 1/3] " Rene Rebe
2024-06-12 18:40         ` Jonathan Wakely
2024-06-12 18:48           ` Jonathan Wakely
2024-06-13  8:58         ` Gerald Pfeifer
2024-06-12 10:42       ` [PATCH 2/3] Enabled LRA for ia64 Rene Rebe
2024-06-12 11:01         ` Richard Biener
2024-06-12 12:50           ` René Rebe
2024-06-12 13:00             ` Richard Biener
2024-06-12 13:19               ` René Rebe
2024-06-12 14:03                 ` Frank Scheiner
2024-06-12 14:09           ` Frank Scheiner
2024-06-12 18:54             ` Jonathan Wakely
2024-06-12 20:59               ` Frank Scheiner
2024-06-13 10:33                 ` Jonathan Wakely
2024-06-13 14:11                   ` Jeff Law
2024-06-13 14:16                     ` Jonathan Wakely
2024-06-13 14:18                       ` Jonathan Wakely
2024-06-14 11:07                   ` Frank Scheiner
2024-06-14 12:53                     ` Jonathan Wakely
2024-06-14 13:07                       ` Frank Scheiner
2024-06-14 13:23                         ` Jonathan Wakely
2024-06-17 18:03                           ` Joseph Myers
2024-06-17 18:53                             ` Jonathan Wakely
2024-06-17 19:36                               ` Frank Scheiner
2024-06-13  7:02             ` Richard Biener
2024-06-12 10:43       ` [PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer Rene Rebe
2024-06-12 19:03         ` Jonathan Wakely
2024-06-12 18:44       ` Jonathan Wakely [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZmnshjFlP_DzWUyX@zen.kayari.org \
    --to=jwakely@redhat.com \
    --cc=frank.scheiner@web.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rene@exactcode.de \
    --cc=rguenther@suse.de \
    /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).