From: Jeffrey Walton <noloader@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: Dirty compile with GCC 7.5
Date: Thu, 2 Jul 2020 01:27:47 -0400 [thread overview]
Message-ID: <CAH8yC8msGm=OZiGYVp0hr9AG9L1hPzHBVp5OCfSUO1M=P3ZQqw@mail.gmail.com> (raw)
tbl_html.c: In function ‘print_tbl’:
tbl_html.c:191:9: warning: ‘%d’ directive output may be truncated
writing between 1 and 10 bytes into a region of size 4
[-Wformat-truncation=]
"%d", dp->hspans + 1);
^~
tbl_html.c:191:8: note: directive argument in the range [2, 2147483647]
"%d", dp->hspans + 1);
^~~~
In file included from /usr/include/stdio.h:862:0,
from tbl_html.c:23:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note:
‘__builtin___snprintf_chk’ output between 2 and 11 bytes into a
destination of size 4
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tbl_html.c:197:9: warning: ‘%d’ directive output may be truncated
writing between 1 and 10 bytes into a region of size 4
[-Wformat-truncation=]
"%d", dp->vspans + 1);
^~
tbl_html.c:197:8: note: directive argument in the range [2, 2147483647]
"%d", dp->vspans + 1);
^~~~
In file included from /usr/include/stdio.h:862:0,
from tbl_html.c:23:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note:
‘__builtin___snprintf_chk’ output between 2 and 11 bytes into a
destination of size 4
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2020-07-02 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 5:27 Jeffrey Walton [this message]
2020-07-02 17:21 ` Ingo Schwarze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8msGm=OZiGYVp0hr9AG9L1hPzHBVp5OCfSUO1M=P3ZQqw@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=discuss@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).