Bug#831449: lintian on Sid amd64 reports volatile false spelling errors in binaries

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

Jakub Wilk wrote:
> It turns out that GCC optimized strcpy() into a series of move instructions.

Maybe one can disable this feature ?
  http://stackoverflow.com/questions/13059044/how-can-i-prevent-strcpy-being-optimised
proposes -fno-builtin-strcpy.

I tried with GNU xorriso and CFLAGS="$CFLAGS -fno-builtin-strcpy".
No change to see in the resulting binary xorriso/xorriso.

But

   CFLAGS="$CFLAGS -fno-builtin"

shows all texts as contiguous strings.

So it seems to be about some other suffix to "-fno-builtin-".
gcc --help does not list any. man gcc gives no list but mentions
"see X86 Built-in Functions". I found:
  https://gcc.gnu.org/onlinedocs/gcc-4.8.5/gcc/X86-Built-in-Functions.html
but this does not mention strcpy.


> I'm not sure what to do about it on Lintian side. Perhaps we should
> spell-check only long (say, >= 12 bytes) strings in binaries?

Actually the binaries seem to be the wrong place to check for typos.
Only a source code parser can surely tell what is a string and what
is a incidential sequence of bytes.


Have a nice day :)

Thomas