public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mkaracsony81 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104069] Wuse-after-free=2 -O0 false positive "may be used"
Date: Wed, 10 May 2023 03:35:31 +0000 [thread overview]
Message-ID: <bug-104069-4-IezHGSwYKY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104069-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104069
Miklos Karacsony <mkaracsony81 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mkaracsony81 at gmail dot com
--- Comment #27 from Miklos Karacsony <mkaracsony81 at gmail dot com> ---
(In reply to Sergei Trofimovich from comment #26)
> #c12 fixed elfutils case.
That's not accurate. It's only fixed if you use the default "-O2" optimization
level, but if you use "-Os" instead, you'll find that the bug is still present.
I've managed to hit a similar bug while building glibc with "-Os" as well, but
in that case adding "--disable-werror" helped. Sadly, elfutils' configure
script does not respect that flag. I could just add "-Wno-error" into my cflags
when building, but then doing this on a per package basis is cumbersome.
next prev parent reply other threads:[~2023-05-10 3:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 17:18 [Bug c/104069] New: -Werror=use-after-free false positive on elfutils-0.186 slyfox at gcc dot gnu.org
2022-01-17 17:27 ` [Bug tree-optimization/104069] " pinskia at gcc dot gnu.org
2022-01-17 17:29 ` slyfox at gcc dot gnu.org
2022-01-17 19:10 ` msebor at gcc dot gnu.org
2022-01-17 21:52 ` msebor at gcc dot gnu.org
2022-01-18 9:37 ` slyfox at gcc dot gnu.org
2022-01-18 22:03 ` msebor at gcc dot gnu.org
2022-01-18 22:06 ` [Bug middle-end/104069] " msebor at gcc dot gnu.org
2022-01-18 22:17 ` jakub at gcc dot gnu.org
2022-01-18 22:47 ` msebor at gcc dot gnu.org
2022-01-18 22:56 ` jakub at gcc dot gnu.org
2022-01-19 0:51 ` amacleod at redhat dot com
2022-01-19 1:04 ` cvs-commit at gcc dot gnu.org
2022-01-19 20:22 ` msebor at gcc dot gnu.org
2022-01-19 20:24 ` msebor at gcc dot gnu.org
2022-01-19 20:30 ` pinskia at gcc dot gnu.org
2022-01-19 20:31 ` pinskia at gcc dot gnu.org
2022-01-19 20:32 ` msebor at gcc dot gnu.org
2022-01-19 20:34 ` jakub at gcc dot gnu.org
2022-01-19 20:42 ` jakub at gcc dot gnu.org
2022-01-19 20:54 ` msebor at gcc dot gnu.org
2022-01-31 11:18 ` jakub at gcc dot gnu.org
2022-03-17 19:32 ` msebor at gcc dot gnu.org
2022-05-16 14:14 ` eike@sf-mail.de
2022-08-24 8:51 ` vincent at systemli dot org
2022-10-27 16:57 ` mark at gcc dot gnu.org
2022-10-28 7:36 ` slyfox at gcc dot gnu.org
2023-05-10 3:35 ` mkaracsony81 at gmail dot com [this message]
2023-05-12 7:00 ` [Bug middle-end/104069] Wuse-after-free=2 -O0 false positive "may be used" slyfox at gcc dot gnu.org
2023-05-12 8:30 ` mkaracsony81 at gmail dot com
2023-05-12 9:08 ` slyfox at gcc dot gnu.org
2023-05-12 13:20 ` mkaracsony81 at gmail dot com
2023-05-12 20:36 ` slyfox at gcc dot gnu.org
2023-05-13 5:07 ` mkaracsony81 at gmail dot com
2023-05-13 5:07 ` mkaracsony81 at gmail dot com
2023-12-17 4:40 ` lavr at ncbi dot nlm.nih.gov
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-104069-4-IezHGSwYKY@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).