public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100307] [11/12 Regression] spurious -Wplacement-new with negative pointer offset
Date: Tue, 04 May 2021 19:51:36 +0000	[thread overview]
Message-ID: <bug-100307-4-RdzzOMP5lf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100307-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:158cdc7bd97d7ccca5bc8adaaf80fe51eacdc038

commit r12-445-g158cdc7bd97d7ccca5bc8adaaf80fe51eacdc038
Author: Martin Sebor <msebor@redhat.com>
Date:   Tue May 4 13:46:37 2021 -0600

    PR middle-end/100307 - spurious -Wplacement-new with negative pointer
offset

    gcc/ChangeLog:

            PR middle-end/100307
            * builtins.c (compute_objsize_r): Clear base0 for pointers.

    gcc/testsuite/ChangeLog:

            PR middle-end/100307
            * g++.dg/warn/Wplacement-new-size-9.C: New test.
            * gcc.dg/tree-ssa/builtin-sprintf-warn-26.c: New test.

  parent reply	other threads:[~2021-05-04 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  6:52 [Bug c++/100307] New: Wrong placement-new warning s.rueckerl at tum dot de
2021-04-28  9:31 ` [Bug c++/100307] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-04-28 10:10 ` jakub at gcc dot gnu.org
2021-04-28 15:55 ` [Bug middle-end/100307] [11/12 Regression] spurious -Wplacement-new with negative pointer offset msebor at gcc dot gnu.org
2021-04-29  1:14 ` msebor at gcc dot gnu.org
2021-05-04 19:51 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-04 19:52 ` [Bug middle-end/100307] [11 " msebor at gcc dot gnu.org
2021-06-17 20:07 ` cvs-commit at gcc dot gnu.org
2021-06-17 20:09 ` msebor 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-100307-4-RdzzOMP5lf@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).