On Sat, Nov 05, 2016 at 11:44:00AM +0000, Ximin Luo wrote: > >> Many software packages (e.g. see #833846) like to set optimisation flags > >> based > I was exaggerating sorry. "some" would match better what I saw myself > directly.
ah. (happens all the time :)
> As for detection, we could get lintian to scan binary packages' pkg-config
> files and perhaps other code-looking files (i.e. not documentation) for
> "-march" and "-mcpu" and "-mtune" but this doesn't cover all cases.
>
> We could also do the same for build logs.
>
> We could also objdump -S binaries and check if they contain illegal
> instructions. For example that's how I detected the presence of AVX/FMA/SSE4
> in linbox, e.g:
>
> $ objdump -S /usr/lib/x86_64-linux-gnu/liblinbox.so | grep
> '\b\(ymm\|zmm\|vfm\)'
>
> but I don't know binary to enough detail to suggest a full set of illegal
> instructions to search for.
me neither :/ So I also have no idea if it's feasable to teach lintian
that and whether we should open a (wishlist) bug report for that
feature. what do you think?
--
cheers,
Holger
signature.asc
Description: Digital signature
