public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102466] -O3 -fsanitize=undefined causes warnings (writing 2 bytes into a region of size 0)
Date: Tue, 29 Mar 2022 14:20:14 +0000 [thread overview]
Message-ID: <bug-102466-4-LHPHy7joNs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102466
Mathieu Malaterre <mathieu.malaterre at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mathieu.malaterre at gmail dot com
--- Comment #3 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> ---
This is also triggered in libjxl codebase:
* https://github.com/libjxl/libjxl/blob/main/tools/fuzzer_corpus.cc
/usr/include/c++/11/bits/stl_algobase.h:431:30: warning: 'void*
__builtin_memmove(void*, const void*, long unsigned int)' writing 1 or more
bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
431 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num);
| ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2022-03-29 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 7:08 [Bug c++/102466] New: " unlvsur at live dot com
2021-09-27 14:00 ` [Bug tree-optimization/102466] " marxin at gcc dot gnu.org
2021-09-27 21:37 ` msebor at gcc dot gnu.org
2022-03-29 14:20 ` mathieu.malaterre at gmail dot com [this message]
2022-03-29 14:22 ` mathieu.malaterre at gmail dot com
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-102466-4-LHPHy7joNs@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).