public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109717] -Warray-bound error with gnu++20 and fmt library
Date: Wed, 03 May 2023 16:37:51 +0000	[thread overview]
Message-ID: <bug-109717-4-vnedw4H1L2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109717-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's not actually broken, it's just paranoid, and the overflow detection
triggers for dead code.

The optimizer analyzes different paths through the code separately, and fails
to detect that some of those paths are unreachable, and then warns that they
would overflow if those paths were taken.

  parent reply	other threads:[~2023-05-03 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 15:35 [Bug c++/109717] New: " psmith at gnu dot org
2023-05-03 15:47 ` [Bug c++/109717] " psmith at gnu dot org
2023-05-03 16:37 ` redi at gcc dot gnu.org [this message]
2023-05-03 20:23 ` [Bug tree-optimization/109717] " psmith at gnu dot org
2023-05-03 20:34 ` redi at gcc dot gnu.org
2023-05-04 11:11 ` [Bug libstdc++/109717] " rguenth at gcc dot gnu.org
2023-05-04 11:13 ` [Bug tree-optimization/109717] " redi at gcc dot gnu.org
2023-05-04 11:16 ` redi at gcc dot gnu.org
2023-05-04 11:37 ` rguenth at gcc dot gnu.org
2023-05-04 13:30 ` psmith at gnu dot 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-109717-4-vnedw4H1L2@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).