From: Xi Ruoyao <xry111@xry111.site>
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>
Subject: Re: [PATCH 2/2] gdb: Remove Itanium (IA-64) architecture
Date: Wed, 08 May 2024 17:43:36 +0800 [thread overview]
Message-ID: <7f65fd9ab40111d1048ed5c9e9447201bee63f26.camel@xry111.site> (raw)
In-Reply-To: <20240508092911.24823-3-yangtiezhu@loongson.cn>
On Wed, 2024-05-08 at 17:29 +0800, Tiezhu Yang wrote:
> The Itanium architecture is obsolete, after the upstream Linux kernel
> commit cf8e8658100d ("arch: Remove Itanium (IA-64) architecture"), the
> IA-64 port has been removed from the Linux kernel, so also remove the
> IA-64 specific code from gdb.
The reasoning is incorrect. The dependency chain of a port is:
- Upstream GCC needs upstream Binutils
- Upstream Linux kernel needs upstream GCC
- Upstream Glibc needs upstream Linux kernel
So the removal of IA64 from the Linux kernel means we should remove it
from Glibc, but you cannot reversely traverse the dependency chain and
claim it should be removed from GCC or Binutils.
Note that I don't mean IA64 shouldn't be removed. I just mean the
reasoning is incorrect, the conclusion may be correct or not.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-05-08 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:29 [PATCH 0/2] binutils-gdb: " 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 [this message]
2024-05-08 12:10 ` Andrew Burgess
2024-05-08 10:05 ` [PATCH 0/2] binutils-gdb: " Frank Scheiner
2024-05-09 1:33 ` 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=7f65fd9ab40111d1048ed5c9e9447201bee63f26.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=kevinb@redhat.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).