Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-20 Thread Bill Allombert
On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote: > Package: gcc-11 > Followup-For: Bug #1005863 > X-Debbugs-Cc: debian-...@lists.debian.org, debian-rele...@lists.debian.org, > debian-pol...@lists.debian.org > > Hi folks, > > Bug #1005863 describes a gcc-11 behaviour that results

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-20 Thread James Addison
On Mon, 20 Mar 2023 at 07:22, Bastian Blank wrote: > > On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote: > > Would it be fair to raise the severity of this bug to a release-critical > > level? > > No, it would be fair to remove Geode LX from the set of supported > processors. Those

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-20 Thread Bastian Blank
On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote: > Would it be fair to raise the severity of this bug to a release-critical > level? No, it would be fair to remove Geode LX from the set of supported processors. Those are now over 15 years old. Bastian -- No one wants war.

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-19 Thread James Addison
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: debian-...@lists.debian.org, debian-rele...@lists.debian.org, debian-pol...@lists.debian.org Hi folks, Bug #1005863 describes a gcc-11 behaviour that results in software that exits ungracefully on Geode LX i686 hardware. Despite

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-19 Thread James Addison
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: martin-eric.rac...@iki.fi > So my guess is that approximately 6-7% of i386 packages in bookworm _that > contain binaries or shared libraries_ are susceptible to this bug. ... > It's also a larger number of packages than we could expect

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-19 Thread James Addison
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: martin-eric.rac...@iki.fi Ok; I should have realised that scanning the entire contents of the i386 bookworm archive for particular opcodes across _all_ files on a single machine seemed to complete surprisingly quickly.. Please find

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-19 Thread James Addison
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: martin-eric.rac...@iki.fi Control: affects -1 + sudo > That's three potential positives; in total, the check ran on approximately > thirty-two thousand (32340, to be more precise) packages. My apologies: there was a bug in the script to

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2023-03-19 Thread James Addison
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: martin-eric.rac...@iki.fi Control: affects -1 - sudo net-tools Control: affects -1 + libjavascriptcoregtk-4.0-18 Control: affects -1 + gobjc++-12-x86-64-linux-gnu Control: affects -1 + libfsapfs-dev Dear Maintainer and Martin-Éric, Using a

Bug#1005863: gcc-11: invalid opcode for Geode LX on i386

2022-02-16 Thread Martin-Éric Racine
Package: gcc-11 Version: 11.2.0-16 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Via "Bug#1004894: sudo: [i386] invalid opcode", at the suggestion of the maintainer, I'm opening this bug. Since 1.9.9-1 'sudo' dumps core on a Geode LX host on i386. Attempts to build from