On Sun, 2023-03-19 at 16:44 +0000, James Addison wrote: > The 'grep' for the word 'nopl' seems potentially fragile. If there's a > more-precise and/or less-false-positive-prone way to check whether each file > contains the 'nopl' opcode (and I'd expect that there is), then that'd be a > welcome improvement. Broadly speaking, detecting non-baseline instruction usage isn't possible without false positives, because the program could use runtime instruction selection based on the current CPU to avoid currently unavailable instructions, while the binary would still contain those instructions for use on other CPUs. https://wiki.debian.org/InstructionSelection Of course you could do the scanning and then use autopkgtests or manual tests to find out if the found programs work on the relevant CPUs. Perhaps lintian could add classification tags for the relevant CPU instructions and then the i386 port could have extra autopkgtest nodes that only process the packages detected by lintian. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part