public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104568] [10/11/12 Regression] ICE [c++20] caused by option "-std=c++20 -Wall" when operand of operator new has size equal to 0
Date: Wed, 16 Feb 2022 19:26:37 +0000	[thread overview]
Message-ID: <bug-104568-4-GF1EP7JaYC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104568-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The code tries to compute how many elements an array with such element type
should have, and obviously when the element size is zero, that doesn't work.
Will need to figure out if the size can be derived from something else or is
completely lost at that point, 0 * anything is 0 but even with zero element
size we might need to know if p[0] or p[23] etc. is valid or not.

  parent reply	other threads:[~2022-02-16 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:02 [Bug c++/104568] New: ICE [regression c++20] " nickhuang99 at hotmail dot com
2022-02-16 17:51 ` [Bug c++/104568] [10/11/12 Regression] ICE [c++20] " pinskia at gcc dot gnu.org
2022-02-16 17:53 ` pinskia at gcc dot gnu.org
2022-02-16 18:29 ` jakub at gcc dot gnu.org
2022-02-16 19:26 ` jakub at gcc dot gnu.org [this message]
2022-02-17 10:08 ` rguenth at gcc dot gnu.org
2022-02-17 15:09 ` jakub at gcc dot gnu.org
2022-03-18 18:02 ` cvs-commit at gcc dot gnu.org
2022-03-18 18:03 ` [Bug c++/104568] [10/11 " jakub at gcc dot gnu.org
2022-03-29  5:54 ` cvs-commit at gcc dot gnu.org
2022-03-30  8:16 ` [Bug c++/104568] [10 " jakub at gcc dot gnu.org
2022-05-10  8:25 ` cvs-commit at gcc dot gnu.org
2022-05-10 10:23 ` 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-104568-4-GF1EP7JaYC@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).