public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steveire at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108197] [12/13 Regression] -Wstringop-overread emitted on simple boost small_vector code
Date: Sat, 24 Dec 2022 17:21:43 +0000	[thread overview]
Message-ID: <bug-108197-4-XYN9bbp9c7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108197-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Stephen <steveire at gmail dot com> ---
Richard, are you saying this a bug in the boost code? It's not quite clear to
me from your message. Can you be more specific about what the bug is in that
case?

  parent reply	other threads:[~2022-12-24 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 10:10 [Bug c++/108197] New: " steveire at gmail dot com
2022-12-22 12:10 ` [Bug tree-optimization/108197] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-12-24 17:21 ` steveire at gmail dot com [this message]
2023-01-13 12:49 ` rguenth at gcc dot gnu.org
2023-04-08 14:38 ` law at gcc dot gnu.org
2023-05-08 12:26 ` [Bug tree-optimization/108197] [12/13/14 " rguenth 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-108197-4-XYN9bbp9c7@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).