On Oct 26, 2025, at 8:54?PM, Jan-Daniel Kaplanski <jd.kaplanski@aol.de> wrote:
?ort on the "Reasons to use Debian" page.[1]
Huh? What is Debian's purpose then? It even boasts about its broad hw supp
Because that's 15 years and Debian's purpose is not to enable retrocomput ing projects.
Besides, the armhf baseline of armv7-a+fp aligns with the Cortex-A8 from 2005[2]. I highly doubt that archaic architecture has a lot of users besides S BCs up to the generation of RPi 2 and legacy embedded systems that are likel
POWER8 went EOSL in 10/2024[5] (only a year ago, which in my books is far away from being a "retrocomputing" platform btw), plus POWER9 systems will re ach the end of standard service on 31st Jan 2026[6], so by the time Forky is
---l user base nor the shelf life of a given architecture. There is the risk yo
As a general guidance I would like to aim for a ten to 15 years support r angeI take issue with that, as this approach does neither reflect on the actua
at release time.
---ive development but likes to keep tabs on what's happening. From the persp ective of a systems administrator, I'm not really fond of the idea of having
That's just my personal take on this as someone who is not involved in act
Cheers, JDinuance-service-select-power-systems-products-replacements-available
[1]: https://www.debian.org/intro/why_debian.en.html
[2]: https://en.wikipedia.org/wiki/ARM_Cortex-A8
[3]: https://en.wikipedia.org/wiki/ARM_Cortex-A53
[4]: https://en.wikipedia.org/wiki/ARM_Cortex-A57
[5]: https://www.ibm.com/new/announcements/ibm-power8-end-of-service
[6]: https://www.ibm.com/docs/en/announcements/services-withdrawal-discont
What is the purpose of this? Is it to, perhaps, reduce work? If so, what
work would that be, specifically?
Is it to give better performance because of greater compiler optimization potential? If so, has anyone done tests that show the advantages of such optimizations? If I recall correctly, at least for amd64, optimizing for newer "v" levels didn't offer measurably meaningful advantages. [1]
Is it to reduce the load on some people or some group or groups of people who'd otherwise need to maintain code supporting older architecture
variants? If so, who are these people / groups, and what work would be
saved?
Is it a desire for cleanliness, and removing older targets makes things more clean?
In other words, what're the real world advantages to these changes, and have they been measured and shown to outweigh the real world disadvantages? If
so, where can we find those evaluations?
Thanks very much,
John Klos
yes - maintaining all special cases is an effort.
yes, but your mileage may vary: You often have a special case where general performance measuerement didb't catch the use case.
yes - that are all people involde in debian or generally in Open Source.
yes, throwing out old clumsy code with special workaround for old hardware flaws
is a great cleanup.
Hi,
On Tue, Oct 28, 2025 at 09:18:38AM +0200, Sicelo wrote:
On Mon, Oct 27, 2025 at 11:52:00PM +0000, John Klos wrote:
What is the purpose of this? Is it to, perhaps, reduce work? If so, what >>> work would that be, specifically?
yes - maintaining all special cases is an effort.
On Oct 26, 2025, at 5:40?AM, Bastian Blank <waldi@debian.org> wrote:
?Hithink
We never did a real discussion about architecture baselines before, but I
we should do that. We also don't have any guidelines what we as Debian want to
actually support. But given that we are a general purpose distribution,we
have to find a balance.ange
As a general guidance I would like to aim for a ten to 15 years support r
at release time. The cutoff in respect to the expected 2027 release dateof
Forky would therefor be 2012 to 2017. More time is given for widely used architectures, less for more specialized ones.d
Bastian
# Current architecture baseline
Only three architectures set an explicit baseline in gcc-12 (Bookworm) an
gcc-15 (Forky):x86].
* armhf: armv7-a+fp
* i386: i686
* s390: z196
All other architectures use the default values.
# Proposal for architecture baseline
## amd64 (and i386)
* x86-64-v2: Supported since around 2008[^x86]. Used in RedHat 9[^redhat9
* x86-64-v3: Supported since around 2013-2015[^x86]. Used in RedHatthe 15
10[^redhat10].
I propose to use the x86-64-v2 baseline in Forky. It gives us more then
years and everyone else already switched to it or even a newer variant. Factoring in a possible LTS for Trixie, this means that x86-64-v1 will stop
being supported by Debian in 2030.seems
## ppc64el
* POWER8: Launched in 2014[^power8].
* POWER9: Launched in 2017[^power9]. Used in RedHat 9[^redhat9] and
10[^redhat10].
I propose to use the POWER9 baseline in Forky. The Debian infrastructure
to be comprised of all POWER9s. This means POWER8 will stop being supported in
2028.ears,
## s390x
* z14: Launched in 2017[^z14]. Used by RedHat 10[^redhat10].
* z15: Launched in 2019[^z15]. Used by next Ubuntu.
I propose to use the z15 baseline in Forky. Yes, this is less then ten y
but s390 is such a niche architecture and all we do is best (often not even
this) effort support. The Debian infrastructure is documented to be at least
z15, all accesible system are actually z16. This means that z14 and older will
stop being support in 2028.rs
# How to see supported baseline
The dynamic linker of glibc can show what microarchiture level it conside
supported on the current CPU. The "supported" marker is relevant in thiscase.
## amd64ibc-hwcaps/,$p'
```
% /usr/lib64/ld-linux-x86-64.so.2 --help | sed -n '/^Subdirectories of gl
Subdirectories of glibc-hwcaps directories, in priority order:,$p'
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
```
## ppc64el
```
% /usr/lib64/ld64.so.2 --help | sed -n '/^Subdirectories of glibc-hwcaps/
Subdirectories of glibc-hwcaps directories, in priority order:^ z15/p'
power10
power9 (supported, searched)
```
## s390x
```
% /usr/lib/ld64.so.1 --help | sed -n '/^Subdirectories of glibc-hwcaps/,/
Subdirectories of glibc-hwcaps directories, in priority order:inux/9/html/9.0_release_notes/architectures
z16 (supported, searched)
z15 (supported, searched)
```
[^power8]: https://en.wikipedia.org/wiki/POWER8
[^power9]: https://en.wikipedia.org/wiki/POWER9
[^x86]: https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels
[^z14]: https://en.wikipedia.org/wiki/IBM_z14_(microprocessor)
[^z15]: https://en.wikipedia.org/wiki/IBM_z15_(microprocessor)
[^redhat9]: https://docs.redhat.com/en/documentation/red_hat_enterprise_l
[^redhat9x86]: https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
[^redhat10]: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/considerations_in_adopting_rhel_10/architectures
--.
Spock: The odds of surviving another attack are 13562190123 to 1, Captain
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:10:34 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |