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 tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector
Date: Thu, 04 Jan 2024 21:10:02 +0000	[thread overview]
Message-ID: <bug-113239-4-jayOA0vKAH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113239-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So I suspect it is either inlining differences due to slightly increased sizes
in some cases or jump threading due to the extra check. I highly doubt that
patch is underlying cause of the warning ...

  reply	other threads:[~2024-01-04 21:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 20:45 [Bug c++/113239] New: " dimitry@unified-streaming.com
2024-01-04 21:10 ` pinskia at gcc dot gnu.org [this message]
2024-01-06 22:49 ` [Bug tree-optimization/113239] " dimitry@unified-streaming.com
2024-01-06 22:53 ` dimitry@unified-streaming.com
2024-01-08 14:57 ` [Bug tree-optimization/113239] [13/14 " rguenth at gcc dot gnu.org
2024-01-21  1:44 ` pinskia at gcc dot gnu.org
2024-01-21  1:46 ` pinskia at gcc dot gnu.org
2024-01-22 16:05 ` fche at redhat dot com
2024-01-22 16:34 ` dimitry@unified-streaming.com
2024-03-07 20:52 ` law at gcc dot gnu.org
2024-05-21  9:18 ` [Bug tree-optimization/113239] [13/14/15 " 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-113239-4-jayOA0vKAH@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).