Hi Andy,
Thus said
Spake? :-)
Can't get the warning here with gcc 7.2.1 20171224 and `-std=c99
-pedantic -pedantic-errors -Wall -Wextra -Wformat=2
-Wno-format-nonliteral'.
It occurred to me that an -O option might make it do more analysis and
trigger the warning so I tried -O{0..3} here, but gcc was still silent.
$ cc -v
Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd6.1/4.2.1/specs
...
gcc version 4.2.1 20070719
So OpenBSD 6.1 from 2017-04-11 ships gcc 4.2.1 from 2007-07-18, ten
years earlier?
Does swapping the strlen and true line above shut it up?
I'm not sure why it would
...
And it still issued the same warning.
I agree it wouldn't make a difference in a sane world, but given gcc is
erroneously complaining in the first place... :-)
Also, I tried compiling the same code on OpenBSD 6.2 which apparently
now uses clang, and I didn't get any warning:
...
$ cc -v
OpenBSD clang version 4.0.0 (tags/RELEASE_400/final) (based on LLVM 4.0.0)
OpenBSD 6.2 from 2017-10-09, Clang 4.0.0 from 2017-03-13.
I think I'm happy enough that nmh compiles on gcc from 10½ year ago
and not too bothered about silencing its faulty warning. But thanks for
pointing it out as different compilers and platforms often spot a bug so
they're worth digging into.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers