public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jonathan.leffler at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111695] Spurious -Wuse-after-free when managing two arrays in parallel
Date: Wed, 04 Oct 2023 18:01:22 +0000 [thread overview]
Message-ID: <bug-111695-4-kuKXSysXWE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111695-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111695
Jonathan Leffler <jonathan.leffler at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56047|0 |1
is obsolete| |
--- Comment #4 from Jonathan Leffler <jonathan.leffler at gmail dot com> ---
Created attachment 56051
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56051&action=edit
gcc-bug-1.c — Variatoion 1 (two arrays in parallel)
prev parent reply other threads:[~2023-10-04 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:57 [Bug c/111695] New: " jonathan.leffler at gmail dot com
2023-10-04 17:58 ` [Bug c/111695] " jonathan.leffler at gmail dot com
2023-10-04 17:59 ` jonathan.leffler at gmail dot com
2023-10-04 18:00 ` jonathan.leffler at gmail dot com
2023-10-04 18:01 ` jonathan.leffler at gmail dot com [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-111695-4-kuKXSysXWE@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).