public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106776] Unexpected use-after-free warning Date: Sat, 22 Oct 2022 01:08:32 +0000 [thread overview] Message-ID: <bug-106776-4-clBLOA386N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106776 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Before PRE [/opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/bits/stl_tree.h:1061:28] __position ={v} {CLOBBER(eol)}; [/app/example.cpp:25:62] _4 = [/app/example.cpp:25:10] &[/app/example.cpp:25:62] [/app/example.cpp:25:62] MEM[(struct pair *)SR.163_98 + 32B].second; [/app/example.cpp:14:23] _57 = MEM[(int *)_3]; [/app/example.cpp:14:21] _58 = _57 + -1; [/app/example.cpp:14:30] MEM[(int *)_3] = _58; [/app/example.cpp:14:17] if (_58 == 0) goto <bb 9>; [33.00%] else goto <bb 10>; [67.00%] <bb 9> [local count: 335388518]: MEM[(int *)_3] ={v} {CLOBBER}; [/app/example.cpp:14:45] operator delete (_3, 4); <bb 10> [local count: 1016328849]: [/opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/bits/stl_pair.h:185:12] D.26938 ={v} {CLOBBER}; [/app/example.cpp:25:37] D.26938 ={v} {CLOBBER(eol)}; [/app/example.cpp:14:23] _54 = MEM[(int *)_3]; So it is not PRE causing the issue ... Look further back.
next prev parent reply other threads:[~2022-10-22 1:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-30 9:12 [Bug middle-end/106776] New: " drfiemost at email dot it 2022-08-30 16:34 ` [Bug middle-end/106776] " msebor at gcc dot gnu.org 2022-09-28 14:33 ` drfiemost at email dot it 2022-10-22 1:08 ` pinskia at gcc dot gnu.org [this message] 2022-10-22 1:24 ` pinskia at gcc dot gnu.org 2022-10-22 1:27 ` pinskia at gcc dot gnu.org 2023-05-30 17:03 ` drfiemost at yahoo 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-106776-4-clBLOA386N@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: linkBe 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).