From: Alejandro Colomar <alx.manpages@gmail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: gcc@gcc.gnu.org
Subject: Re: [BUG] missing warning for pointer arithmetic out of bounds
Date: Tue, 13 Dec 2022 20:24:47 +0100 [thread overview]
Message-ID: <e0161f0b-8eea-ad77-d49d-ac3f263f2c26@gmail.com> (raw)
In-Reply-To: <B9E38906-88DC-45CE-94AB-72DEF6A590B2@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 1611 bytes --]
Hi Paul,
On 12/13/22 20:22, Paul Koning wrote:
>
>
>> On Dec 13, 2022, at 2:08 PM, Alejandro Colomar via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> Hi!
>>
>> For the following program:
>>
>>
>> $ cat buf.c
>> #include <stdio.h>
>>
>> int main(void)
>> {
>> char *p, buf[5];
>>
>> p = buf + 6;
>> printf("%p\n", p);
>> }
>>
>>
>> There are no warnings in gcc, as I would expect:
>>
>> $ gcc -Wall -Wextra buf.c -O0
>>
>> Clang does warn, however:
>>
>> $ clang -Weverything -Wall -Wextra buf.c -O0
>> buf.c:8:17: warning: format specifies type 'void *' but the argument has type 'char *' [-Wformat-pedantic]
>> printf("%p\n", p);
>> ~~ ^
>> %s
>> buf.c:7:6: warning: the pointer incremented by 6 refers past the end of the array (that contains 5 elements) [-Warray-bounds-pointer-arithmetic]
>> p = buf + 6;
>> ^ ~
>
> I thought void * is a generic pointer that accepts any pointer argument. So a warning about char* being passed in seems to be flat out wrong.
>
>> buf.c:5:2: note: array 'buf' declared here
>> char *p, buf[5];
>> ^
>> 2 warnings generated.
>
> That was discussed just days ago: C says that a pointer one past the end of the array is legal. So here too it looks like Clang is wrong and GCC is right.
Look again:
char *p, buf[5];
p = buf + 6;
That's a pointer two-past-the-end; not one.
That's UB.
Cheers,
Alex
>
> paul
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-13 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:08 Alejandro Colomar
2022-12-13 19:15 ` Alejandro Colomar
2022-12-13 19:18 ` Andrew Pinski
2022-12-18 12:48 ` Optimization levels for getting all warnings (was: [BUG] missing warning for pointer arithmetic out of bounds) Alejandro Colomar
2022-12-13 19:22 ` [BUG] missing warning for pointer arithmetic out of bounds David Malcolm
2022-12-13 19:22 ` Paul Koning
2022-12-13 19:24 ` Alejandro Colomar [this message]
2022-12-13 20:45 ` Jonathan Wakely
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=e0161f0b-8eea-ad77-d49d-ac3f263f2c26@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=paulkoning@comcast.net \
/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).