public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94335] [10/11 Regression] False positive -Wstringop-overflow warning with -O2
Date: Thu, 11 Jun 2020 15:28:42 +0000	[thread overview]
Message-ID: <bug-94335-4-jy2uK27ELY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94335-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to kal.conley from comment #6)

For reference, this was also submitted as pr95353 and is now fixed on trunk
(GCC 11).

The test case in comment #0 still triggers a warning.

  parent reply	other threads:[~2020-06-11 15:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 22:35 [Bug tree-optimization/94335] New: " romain.geissler at amadeus dot com
2020-03-26  0:07 ` [Bug tree-optimization/94335] " msebor at gcc dot gnu.org
2020-03-26  0:50 ` romain.geissler at amadeus dot com
2020-03-26  7:01 ` rguenth at gcc dot gnu.org
2020-03-26  8:24 ` marxin at gcc dot gnu.org
2020-03-26  8:42 ` romain.geissler at amadeus dot com
2020-03-26 19:39 ` msebor at gcc dot gnu.org
2020-05-20 13:10 ` kal.conley at dectris dot com
2020-05-20 15:15 ` [Bug tree-optimization/94335] [10/11 Regression] " msebor at gcc dot gnu.org
2020-06-11 15:28 ` msebor at gcc dot gnu.org [this message]
2020-06-26 12:04 ` rguenth at gcc dot gnu.org
2020-07-23  6:52 ` rguenth at gcc dot gnu.org
2021-01-21 22:45 ` msebor at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-09-21  8:34 ` [Bug tree-optimization/94335] [10/11/12 " pinskia at gcc dot gnu.org
2021-09-21  9:43 ` pinskia at gcc dot gnu.org
2021-11-23 10:24 ` pinskia at gcc dot gnu.org
2022-06-28 10:40 ` [Bug tree-optimization/94335] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug tree-optimization/94335] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-10 21:46 ` law 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-94335-4-jy2uK27ELY@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).