Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Jens Remus <jremus@linux.ibm.com>
Cc: gdb-patches@sourceware.org, Andreas Arnez <arnez@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	binutils@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>,
	Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [PATCH v1 0/1] s390: Deprecate s390 32-bit target "s390-*"
Date: Thu, 16 Apr 2026 08:21:17 +0200	[thread overview]
Message-ID: <25375ebb-f5df-4dd1-8385-0cad3409f36e@suse.com> (raw)
In-Reply-To: <20260413114052.2415966-1-jremus@linux.ibm.com>

On 13.04.2026 13:40, Jens Remus wrote:
> 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 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.

When we discussed merely deprecation (not removal) of Xeon Phi support
on x86, we decided to wait with that until the last gcc version
supporting it went out of support. Maybe best to follow a similar time
line here, at least for the "removal" part.

Jan

      parent reply	other threads:[~2026-04-16  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 11:40 Jens Remus
2026-04-13 11:40 ` [PATCH v1 1/1] " Jens Remus
2026-04-16  6:21 ` Jan Beulich [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=25375ebb-f5df-4dd1-8385-0cad3409f36e@suse.com \
    --to=jbeulich@suse.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=jremus@linux.ibm.com \
    --cc=krebbel@linux.ibm.com \
    --cc=law@redhat.com \
    --cc=nickc@redhat.com \
    --cc=rdsandiford@googlemail.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