public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution
Date: Fri, 21 Jan 2022 13:42:26 +0000 [thread overview]
Message-ID: <bug-99673-4-adA8zI9mi2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99673-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #1)
> A further reduced/simplified test case is below. The root cause is similar
> to the one discussed in pr99578 comment 8.
>
> $ cat pr99673.c && gcc -Os -S -Wall -fsanitize=address
> -fno-inline-functions-called-once -m32 pr99673.c
This was fixed with r12-5465-g911b633803dcbb29 and started with
r11-3305-gbaad4c48a85a354d.
next prev parent reply other threads:[~2022-01-21 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:59 [Bug sanitizer/99673] New: [11 Regression] bogus -Wstringop-overread warning with address sanitizer arnd at linaro dot org
2021-03-19 21:44 ` [Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution msebor at gcc dot gnu.org
2021-03-20 12:22 ` arnd at linaro dot org
2021-03-21 19:06 ` msebor at gcc dot gnu.org
2021-03-22 8:51 ` rguenth at gcc dot gnu.org
2021-03-22 16:07 ` arnd at linaro dot org
2021-04-08 13:09 ` rguenth at gcc dot gnu.org
2021-04-27 11:40 ` [Bug sanitizer/99673] [11/12 " jakub at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2022-01-21 12:50 ` [Bug sanitizer/99673] [11 " rguenth at gcc dot gnu.org
2022-01-21 12:59 ` cvs-commit at gcc dot gnu.org
2022-01-21 13:42 ` marxin at gcc dot gnu.org [this message]
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2022-05-05 12:42 ` [Bug sanitizer/99673] [11/13 " rguenth at gcc dot gnu.org
2023-05-29 10:04 ` [Bug sanitizer/99673] [11/13/14 " jakub at gcc dot gnu.org
2024-03-27 7:37 ` pinskia 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-99673-4-adA8zI9mi2@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).