This looks relevant: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84148
Cheers, Julien On Wed, Mar 10, 2021 at 11:20:25AM +0100, Bernhard Übelacker wrote: > Hello Martin-Éric, > without being involved in packaging fwupd I tried to > have a look at this issue. > > I could not reproduce it inside a i386 qemu VM (not even > with "-cpu pentium"). Have not tested on real hardware. > > > Looking up the endbr32 instruction, it seems it belongs to something > called "Control-flow Enforcement Technology" (CET, indirect branch) [1]. > > The opcode for this instruction got selected to run on old > CPUs as NOP, but it looks like your CPU handles it differently. > From the system name it is some "geode" CPU? > > (In [2] someone mentions also a illegal instruction > for a geode CPU with the endbr32 instruction.) > > > Maybe you could add to this bug report the output of > 'lscpu' or 'cat /proc/cpuinfo' ? > > Then the maintainer might be able to tell if this CPU > meets the Debian baseline requirements for bullseye. > ([3], maybe outdated? Is there a better "baseline" description?) > > > Kind regards, > Bernhard > > [1] > https://www.linuxplumbersconf.org/event/2/contributions/147/attachments/72/83/CET-LPC-2018.pdf > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84148#c3 > [3] https://wiki.debian.org/ArchitectureSpecificsMemo#i386-1 >