public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tonyfettes at tonyfettes dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/103145] New: False positive of -Wstringop-overread on gcc-11
Date: Tue, 09 Nov 2021 02:56:45 +0000	[thread overview]
Message-ID: <bug-103145-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103145

            Bug ID: 103145
           Summary: False positive of -Wstringop-overread on gcc-11
           Product: gcc
           Version: 11.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tonyfettes at tonyfettes dot com
  Target Milestone: ---

Hi,

The following piece of code will trigger -Wstringop-overread

$ cat test.c
// test.c
#include <stdio.h>

#define ARRAY_SIZE 4

struct func_in_t {
  int x;
  int y;
};

struct example_t {
  int field0;
  int field1;
  int field2;
  int field3;
  int field4;
};

struct example_t func(const struct func_in_t *in, const int array[ARRAY_SIZE])
{
  struct example_t out = {0};
  return out;
}

int main() {
  int array[ARRAY_SIZE] = { 0, 0, 0, 0 };
  struct func_in_t in = {
    .x = 0,
    .y = 0,
  };
  struct example_t col = func(&in, array);
  (void) col;
  return 0;
}

$ gcc -fno-strict-aliasing -fwrapv -Wall test.c -o test 
test.c: In function ‘main’:
test.c:30:26: warning: ‘func’ reading 16 bytes from a region of size 8
[-Wstringop-overread]
   30 |   struct example_t col = func(&in, array);
      |                          ^~~~~~~~~~~~~~~~
test.c:30:26: note: referencing argument 2 of type ‘const int *’
test.c:19:18: note: in a call to function ‘func’
   19 | struct example_t func(const struct func_in_t *in, const int
array[ARRAY_SIZE]) {
      |                  ^~~~

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --with-isl
--with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit
--enable-cet=auto --enable-checking=release --enable-clocale=gnu
--enable-default-pie --enable-default-ssp --enable-gnu-indirect-function
--enable-gnu-unique-object --enable-install-libiberty --enable-linker-build-id
--enable-lto --enable-multilib --enable-plugin --enable-shared
--enable-threads=posix --disable-libssp --disable-libstdcxx-pch
--disable-libunwind-exceptions --disable-werror
gdc_include_dir=/usr/include/dlang/gdc
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.1.0 (GCC) 

It seems like a duplication of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101854, but I'm not sure about it
since gcc gave different diagnostics (one is overread, the other is overflow),
so I decide to submit it anyway.

             reply	other threads:[~2021-11-09  2:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  2:56 tonyfettes at tonyfettes dot com [this message]
2021-11-09 19:38 ` [Bug tree-optimization/103145] " msebor at gcc dot gnu.org
2021-11-09 19:40 ` [Bug tree-optimization/103145] [11 Regression] bogus -Wstringop-overread with an array argument msebor at gcc dot gnu.org
2021-11-16 13:09 ` rguenth at gcc dot gnu.org
2021-11-18 15:45 ` redi at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` jakub at gcc dot gnu.org

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=bug-103145-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).