On 27 March 2012 07:34, Mike Thompson <mpthomp...@gmail.com> wrote: > I came across something that should help significantly with the problem of > determining if there is ARMv7 code leakage into my recompiled armhf packages > that should be ARMv6 pure. > > Basically, I can use the 'readelf -A' command to determine when a v6 > executable has been linked against a v7 static library, thus causing > contamination of v7 code into my packages. > > It seems to work as follows. Below, in my armhf v6 chroot environment I > compiled the hello.c program using my rebuilt v6 gcc and linked it against > the rebuilt v6 standard C libraries. As shown below 'readelf -A' does > indeed properly report the resulting binary as pure v6 code.
If you identify the v7 instructions that are not in v6, you can use something like the attached, which I wrote to count the percentage of MaverickCrunch instructions in the binaries in a Debian package. As it stands, it disassenbles all object files contained a list of Debian package and reports the percentage of instructions that involve floating point. You'd need to modify it to identify by name the v7-specific instructions (the "greo ".... cf" line) and to print the names of offending packages instead of a count - that would narrow it down to the binary package level Enjoy M
dpkg-cfdensity
Description: Binary data
