Bug#1005863: gcc: should reject combination of i686 architecture and fcf-protection feature

2023-03-24 Thread James Addison
Followup-For: Bug #1005863 Control: affects -1 = sudo

Bug#1005863: binutils: invalid opcode for Geode LX on i386

2023-03-20 Thread James Addison
Followup-For: Bug #1005863 X-Debbugs-Cc: ballo...@debian.org Control: reassign -1 binutils 2.38-1 Reassigning this from package 'gcc' to 'binutils': It looks like it is GNU binutils[1] (and in particular, the GNU assembler) that is responsible for producing the assembly opcodes for a binary

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 suppor

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-gcc@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#1023666: gcc-10 should not be shipped in bookworm

2023-02-28 Thread James Addison
Package: gcc-10 Version: 10.4.0-7 Followup-For: Bug #1023666 Bug #1004184 implies that gcc-11 cannot build correct mips64 code for a key Debian package (source: matplotlib) without buildflag adjustments. However, gcc-10 does emit correct code for the same package and architecture. Should that

Bug#1004184: gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el

2023-02-24 Thread James Addison
Source: gcc-11 Followup-For: Bug #1004184 X-Debbugs-Cc: frederic-emmanuel.pi...@synchrotron-soleil.fr Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104914 Hi Frederic: I'm linking a forwarded GCC GNU bug report that I _think_ is the upstream report matching this bug. I found