Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jens Remus <jremus@linux.ibm.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
	Nick Clifton <nickc@redhat.com>, Ian Lance Taylor <ian@airs.com>,
	Jeff Law <law@redhat.com>, Jim Wilson <wilson@tuliptree.org>,
	DJ Delorie <dj@redhat.com>, Alan Modra <amodra@gmail.com>,
	Michael Meissner <gnu@the-meissners.org>,
	Richard Sandiford <rdsandiford@googlemail.com>,
	Jan Beulich <jbeulich@suse.com>,
	Andreas Krebbel <krebbel@linux.ibm.com>,
	Andreas Arnez <arnez@linux.ibm.com>
Cc: Jens Remus <jremus@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Stefan Liebler <stli@linux.ibm.com>
Subject: [PATCH v2 0/1] s390: Deprecate s390 32-bit target "s390-*"
Date: Thu, 23 Apr 2026 14:00:05 +0200	[thread overview]
Message-ID: <20260423120006.3740571-1-jremus@linux.ibm.com> (raw)

Linux Kernel 6.19 removed s390 32-bit compatibility support. [1]
Glibc 2.43 deprecated s390 32-bit [2] and will remove it with
Glibc 2.44 [3].  GCC 16 will deprecate s390 32-bit (compiler option
-m31) with the intent to remove it in a future release. [4]

This deprecates s390 32-bit (target "s390-*" and format "elf32-s390")
in the upcoming Binutils and GDB release with the intent to remove it
in a future release.

s390 32-bit deprecation/removal overview:
- Linux Kernel 6.19 (February 2026) removed s390 32-bit compat
- Glibc 2.43 (January 2026) deprecated s390 32-bit
- GCC 16 (expected April 2026) will deprecate s390 32-bit
- Glibc 2.44 (expected August 2026) will remove s390 32-bit
- Binutils 2.47 (expected August 2026) would deprecate s390 32-bit
- Binutils 2.48 (expected February 2027) would remove s390 32-bit
- GCC 17 (expected April 2027) would remove s390 32-bit

Removal of s390 32-bit support in Binutils could also be deferred to
Binutils 2.49 (expected August 2027) if that would be preferable, so
that Binutils removes it after GCC.

Note that the error is actually not issued during a toplevel configure,
as configure in bfd/ is actually deferred to make.  Should this be
improved, for instance by replicating commit 91fb2a9d47c5 ("Add code to
catch obsolete configurations ...") to configure.ac?

Changes in v2:
- Add likewise gdb/NEWS entry, as the deprecation/removal in also
  affects GDB.

Feedback is much appreciated!

[1]: Linux kernel 6.19 commit 8e0b986c59c6 ("s390: Remove compat support"),
     https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8e0b986c59c6
[2]: Glibc 2.43 commit 638d437dbf9c ("Deprecate s390-linux-gnu (31bit)"),
     https://sourceware.org/git/glibc.git?a=commitdiff;h=638d437dbf9c
[3]: Glibc 2.44 patch series "[PATCH 0/5] Remove s390-linux-gnu (31bit)",
     https://inbox.sourceware.org/libc-alpha/20260409085102.3475867-1-stli@linux.ibm.com/
[4]: GCC 16 commit 5886bb453a6a ("s390: Deprecate -m31"),
     https://gcc.gnu.org/git/gcc.git?h=5886bb453a6a

Thanks and regards,
Jens

Jens Remus (1):
  s390: Deprecate s390 32-bit target "s390-*"

 bfd/config.bfd |  1 +
 binutils/NEWS  |  8 ++++++++
 gdb/NEWS       | 13 +++++++++++++
 3 files changed, 22 insertions(+)

-- 
2.51.0


             reply	other threads:[~2026-04-23 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 12:00 Jens Remus [this message]
2026-04-23 12:00 ` [PATCH v2 1/1] " Jens Remus
2026-06-22 12:12 ` [PATCH v2 0/1] " Jens Remus
     [not found] ` <6c8ebd42-d0af-43c0-add9-6e9dc906f771@linux.ibm.com>
2026-07-06  9:00   ` Andreas Arnez
2026-07-06 14:45     ` Jens Remus

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=20260423120006.3740571-1-jremus@linux.ibm.com \
    --to=jremus@linux.ibm.com \
    --cc=amodra@gmail.com \
    --cc=arnez@linux.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gnu@the-meissners.org \
    --cc=ian@airs.com \
    --cc=iii@linux.ibm.com \
    --cc=jbeulich@suse.com \
    --cc=krebbel@linux.ibm.com \
    --cc=law@redhat.com \
    --cc=nickc@redhat.com \
    --cc=rdsandiford@googlemail.com \
    --cc=stli@linux.ibm.com \
    --cc=wilson@tuliptree.org \
    /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