Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.ibm.com>
To: Andreas Krebbel <krebbel@linux.ibm.com>
Cc: Jens Remus <jremus@linux.ibm.com>,
	binutils@sourceware.org, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 0/1] s390: Deprecate s390 32-bit target "s390-*"
Date: Mon, 06 Jul 2026 11:00:51 +0200	[thread overview]
Message-ID: <877bn8o5ks.fsf@li-07e5db4c-3052-11b2-a85c-815382633c95.ibm.com> (raw)
In-Reply-To: <6c8ebd42-d0af-43c0-add9-6e9dc906f771@linux.ibm.com> (Andreas Krebbel's message of "Thu, 2 Jul 2026 17:02:47 +0200")

On Thu, Jul 02 2026, Andreas Krebbel wrote:

> Hi Jens,
>
> On 4/23/26 2:00 PM, 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 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.
> I think would be ok to require GCC users of a deprecated feature to use an
> older Binutils version.  I'm ok with dropping it with 2.48 already.
>>
>> 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?
> I don't think it is worth the trouble for something which will be removed
> soon anyway.
>
> Patch is ok. Thank you, Jens!
>
> Bye
>>
>> Changes in v2:
>> - Add likewise gdb/NEWS entry, as the deprecation/removal in also
>>    affects GDB.

This looks OK to me.

>>
>> 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(+)
>>
>

-- 
Andreas

  parent reply	other threads:[~2026-07-06  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 12:00 Jens Remus
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 [this message]
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=877bn8o5ks.fsf@li-07e5db4c-3052-11b2-a85c-815382633c95.ibm.com \
    --to=arnez@linux.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jremus@linux.ibm.com \
    --cc=krebbel@linux.ibm.com \
    /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