public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xavier.cooney03 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111730] New: erroneous alloc-size-larger-than warning with -O1
Date: Mon, 09 Oct 2023 01:12:47 +0000	[thread overview]
Message-ID: <bug-111730-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111730
           Summary: erroneous alloc-size-larger-than warning with -O1
           Product: gcc
           Version: 13.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: xavier.cooney03 at gmail dot com
  Target Milestone: ---

Created attachment 56076
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56076&action=edit
bug.c

Hi, in some circumstances gcc incorrectly emits the alloc-size-larger-than
warning:

$ gcc -O1 -Wall -c bug.c
bug.c: In function ‘foo’:
bug.c:9:15: warning: argument 1 range [18446744071562067968,
18446744073709551615] exceeds maximum object size 9223372036854775807
[-Walloc-size-larger-than=]
    9 |     char *a = malloc(x);
      |               ^~~~~~~~~
bug.c:4:14: note: in a call to allocation function ‘malloc’ declared here
    4 | extern void *malloc (size_t size) __attribute__ ((__malloc__));
      |              ^~~~~~


This only seems to occur when using -O1, other optimisation levels (-O0, -O2,
-O3, -Os) don't result in the warning.

The 'useless' loops are necessary to reproduce, removing the first or last loop
causes the warning to disappear.

18446744071562067968 = 0xffffffff80000000
18446744073709551615 = 0xffffffffffffffff

It seems as if gcc is incorrectly deducing that `x` must be negative.

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure
--enable-languages=ada,c,c++,d,fortran,go,lto,objc,obj-c++ --enable-bootstrap
--prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--with-build-config=bootstrap-lto --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-libstdcxx-backtrace --enable-link-serialization=1
--enable-linker-build-id --enable-lto --enable-multilib --enable-plugin
--enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch
--disable-werror
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.1 20230801 (GCC)

             reply	other threads:[~2023-10-09  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  1:12 xavier.cooney03 at gmail dot com [this message]
2023-10-09  1:36 ` [Bug c/111730] " pinskia at gcc dot gnu.org
2023-10-09  2:08 ` [Bug tree-optimization/111730] " pinskia at gcc dot gnu.org
2023-10-09  2:15 ` pinskia at gcc dot gnu.org
2023-10-09  2:38 ` xavier.cooney03 at gmail dot com

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-111730-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).