From: Xi Ruoyao <ryxi@stu.xidian.edu.cn>
To: Martin Sebor <msebor@gmail.com>, gcc-patches@gcc.gnu.org
Cc: ryxi@stu.xidian.edu.cn
Subject: Re: [PATCH 2/6] New warnings -Wstring-plus-{char, int} (PR c++/62181)
Date: Mon, 19 Jun 2017 17:28:00 -0000 [thread overview]
Message-ID: <1497893292.8943.1.camel@stu.xidian.edu.cn> (raw)
In-Reply-To: <699bc809-8e5f-b908-7b2e-0dd036a09462@gmail.com>
On 2017-06-19 10:51 -0600, Martin Sebor wrote:
> On 06/11/2017 07:32 PM, Xi Ruoyao wrote:
> > This patch adds warning option -Wstring-plus-int for C/C++.
> >
> > gcc/ChangeLog:
> >
> > 2017-06-12  Xi Ruoyao  <ryxi@stu.xidian.edu.cn>
> >
> > * c-family/c.opt: New option -Wstring-plus-int.
> > * c-family/c-common.c (pointer_int_sum): Checking for
> > -Wstring-plus-int.
>
> This is a very useful warning but I would suggest to word it
> in terms of what it actually does rather than what it might be
> intended to do.  E.g., for
>
> Â Â Â const char *p = "123" + 7;
>
> issue
>
> Â Â Â warning: offset 7 exceeds the upper bound 3 of the array
>
> rather than
>
> Â Â Â warning: adding 'int' to a string does not append to the string
>
> (I have trouble envisioning on what grounds someone might expect
> the addition to have this effect.)
How about something like `const char *p = "123" + getchar();` ?
I'd like this for -Wstring-plus-int=1:
warning: adding 'int' to a string does not append to the string
[-Wstring-plus-int=]
const char *p = "123" + 7;
^
note: offset 7 exceeds the size 4 of the string, using the result
may lead to undefined behaviour.
(Clang permits "123" + 4 since its result is well defined in standard.
Maybe we could permit "123" + 3 only.)
For level 1 we only warn for such obvious mistakes. And for
-Wstring-plus-int=2:
warning: adding 'int' to a string does not append to the string
[-Wstring-plus-int=]
const char *p = "123" + getchar();
^
note: the offset may exceed the size of the string.
(Clang also warn while it's impossible to know whether the offset
exceeds. It seems aggressively so we can make it level 2.)
> Given that the warning only triggers when the upper bound of
> an array is exceeded I would also suggest to consider including
> the warning in -Warray-bounds.  (With that, it would be useful
> to also detect exceeding the upper bound of non-literal arrays
> as well.)
We can let -Warray-bounds enable -Wstring-plus-int=1, but not =2.
--
Xi Ruoyao <ryxi@stu.xidian.edu.cn>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2017-06-19 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 1:26 [PATCH 0/6] " Xi Ruoyao
2017-06-12 1:31 ` [PATCH 1/6] " Xi Ruoyao
2017-06-12 1:32 ` [PATCH 2/6] " Xi Ruoyao
2017-06-19 16:51 ` Martin Sebor
2017-06-19 17:28 ` Xi Ruoyao [this message]
2017-06-19 18:44 ` Martin Sebor
2017-06-19 19:36 ` Xi Ruoyao
2017-06-22 10:26 ` Xi Ruoyao
2017-07-15 16:33 ` Gerald Pfeifer
2017-06-12 1:34 ` [PATCH 3/6] " Xi Ruoyao
2017-06-19 16:30 ` Martin Sebor
2017-06-19 17:35 ` Xi Ruoyao
2017-06-12 1:36 ` [PATCH 4/6] " Xi Ruoyao
2017-06-12 1:39 ` [PATCH 5/6] " Xi Ruoyao
2017-06-12 1:39 ` [PATCH 6/6] " Xi Ruoyao
2017-06-19 16:57 ` Martin Sebor
2017-06-19 12:43 ` [PING PATCH 0/6] " Xi Ruoyao
2017-06-19 16:20 ` [PATCH " Martin Sebor
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=1497893292.8943.1.camel@stu.xidian.edu.cn \
--to=ryxi@stu.xidian.edu.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).