public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109308] False positive store to address 0x62600000016c with insufficient space for an object of type 'int' since r12-6030-g422f9eb7011b76c1
Date: Tue, 28 Mar 2023 05:34:37 +0000	[thread overview]
Message-ID: <bug-109308-4-Kcyn5gk9D4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109308-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This code is very much undefined.
THe original code did:
  opc = XNEWVEC (struct m68hc11_opcode_def, num_opcodes);
  m68hc11_opcode_defs = opc--;

Which is definitely undefined. You cannot take the address before the allocated
memory and have it be defined. The only address which is valid is where the
array starts and one element past the allocation.

  parent reply	other threads:[~2023-03-28  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  3:30 [Bug sanitizer/109308] New: " marxin at gcc dot gnu.org
2023-03-28  3:31 ` [Bug sanitizer/109308] " marxin at gcc dot gnu.org
2023-03-28  5:09 ` pinskia at gcc dot gnu.org
2023-03-28  5:33 ` marxin at gcc dot gnu.org
2023-03-28  5:34 ` pinskia at gcc dot gnu.org [this message]
2023-03-28  8:56 ` amodra at gmail dot com
2023-03-28 12:53 ` siddhesh 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-109308-4-Kcyn5gk9D4@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).