public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ishikawa at yk dot rim.or.jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109041] Bogus compile time check by __builtin_memset? error: ‘__builtin_memset’ writing 4 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
Date: Fri, 10 Mar 2023 14:49:49 +0000	[thread overview]
Message-ID: <bug-109041-4-Tpd5qmdqw3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109041-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from ishikawa,chiaki <ishikawa at yk dot rim.or.jp> ---
Thank you for the confirmation for the fix in GCC-12.

Now I have to figure out how GCC-12 seems to miscompile something in
Thunderbird mail client to report a run-time assertion error.
(Compiling Thunderbird mail client with earlier version did not show the
runtime assertion error. So I wanted to weed out possible source problem from
mozilla source code and thunderbird mail client code by using -Werror with due
caution.)

Thank you again for the confirmation of the fix in GCC-12.

      parent reply	other threads:[~2023-03-10 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 11:16 [Bug c/109041] New: " ishikawa at yk dot rim.or.jp
2023-03-06 16:40 ` [Bug tree-optimization/109041] " pinskia at gcc dot gnu.org
2023-03-07 15:52 ` ishikawa at yk dot rim.or.jp
2023-03-07 15:56 ` pinskia at gcc dot gnu.org
2023-03-08  1:14 ` pinskia at gcc dot gnu.org
2023-03-08  5:11 ` ishikawa at yk dot rim.or.jp
2023-03-08 10:02 ` marxin at gcc dot gnu.org
2023-03-08 15:52 ` ishikawa at yk dot rim.or.jp
2023-03-08 15:55 ` ishikawa at yk dot rim.or.jp
2023-03-09 11:09 ` marxin at gcc dot gnu.org
2023-03-10 14:49 ` ishikawa at yk dot rim.or.jp [this message]

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-109041-4-Tpd5qmdqw3@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).