public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Frank Scheiner <frank.scheiner@web.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
	binutils@sourceware.org, gdb-patches@sourceware.org
Cc: "Jim Wilson" <wilson@tuliptree.org>,
	"Jeff Johnston" <jjohnstn@redhat.com>,
	"Kevin Buettner" <kevinb@redhat.com>,
	"Tomáš Glozar" <tglozar@gmail.com>,
	"René Rebe" <rene@exactcode.de>
Subject: Re: [PATCH 0/2] binutils-gdb: Remove Itanium (IA-64) architecture
Date: Wed, 8 May 2024 12:05:36 +0200	[thread overview]
Message-ID: <1e346375-165d-43fb-9c60-b915e68d1350@web.de> (raw)
In-Reply-To: <20240508092911.24823-1-yangtiezhu@loongson.cn>

Hi there,

On 08.05.24 11:29, Tiezhu Yang wrote:
> The Itanium architecture is obsolete, the IA-64 port has been removed
> from the upstream Linux kernel, this series attempts to remove it in
> binutils-gdb.git.
>
> Please let me know whether it is time to do this work, any comments
> will be much appreciated.

from our point of view it is not yet time for it as ia64 is neither
obsolete nor broken. You might not be aware, but we are since a while
working on getting ia64 back into the Linux kernel and it is
successfully maintained out of tree since nearly 3 mainline releases
now. You can read up on our progress on [1] and [2] and after the
release message for v6.9 on the LKML.

[1]:
https://lore.kernel.org/all/fe5f6e9b-02a2-42e9-8151-ae4b6fdba7e3@web.de/

[2]:
https://lore.kernel.org/all/145da253-b3bc-43da-a262-a3ebdfbea5a2@web.de/

The HP Sim platform was also restored in the meantime, so people can
test ia64 software on e.g. x86_64, up to mainline. See the Linux stable
release (candidate) builds on [3] for example, all still maintained
stable kernels work in Ski with HP Sim as platform.

[3]: https://github.com/linux-ia64/linux-stable-rc/actions/runs/8995653713

Each mainline release (candidate) was/is also regularly cross-compiled
with binutils 2.41/2.42 (since a while) and the latest gcc-14 (now
gcc-15) snapshot since beginning of the year. The result was/is tested
on the following real machines:

* rx2620 (w/Montecito)
* rx4640 (w/Madison)
* rx2660 (w/Montecito)
* rx6600 (w/Montvale)
* rx2800 i2 (w/Tukwila)

...and of course also in Ski with the HP Sim platform. All that w/o any
showstopping issues related to binutils or gcc. For the gcc
cross-compiler LRA was also enabled recently, also w/o any negative
effect on the resulting kernels.

****

So is there something broken in binutils for ia64 that we don't know of
maybe?

Cheers,
Frank

  parent reply	other threads:[~2024-05-08 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  9:29 Tiezhu Yang
2024-05-08  9:29 ` [PATCH 1/2] binutils: " Tiezhu Yang
2024-05-08  9:29 ` [PATCH 2/2] gdb: " Tiezhu Yang
2024-05-08  9:43   ` Xi Ruoyao
2024-05-08 12:10   ` Andrew Burgess
2024-05-08 10:05 ` Frank Scheiner [this message]
2024-05-09  1:33   ` [PATCH 0/2] binutils-gdb: " Tiezhu Yang

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=1e346375-165d-43fb-9c60-b915e68d1350@web.de \
    --to=frank.scheiner@web.de \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jjohnstn@redhat.com \
    --cc=kevinb@redhat.com \
    --cc=rene@exactcode.de \
    --cc=tglozar@gmail.com \
    --cc=wilson@tuliptree.org \
    --cc=yangtiezhu@loongson.cn \
    /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).