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 tree-optimization/107467] [12/13 Regression] Miscompilation involing -Os , -flto and -fno-strict-aliasing
Date: Wed, 28 Dec 2022 10:07:49 +0000 [thread overview]
Message-ID: <bug-107467-4-3Xj1O5XFhr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107467-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107467
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org
Keywords|needs-bisection |
Status|ASSIGNED |NEW
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Running that under valgrind I see it started with r12-656-ga564da506f52be66:
==13643== Conditional jump or move depends on uninitialised value(s)
==13643== at 0x401148: bool compare_pairs<SomeClass*>(pair<SomeClass*>
const&, pair<SomeClass*> const&) (pr107467-2.C:12)
==13643== by 0x401176: Combined<OtherClass>::clashy() [clone .isra.0]
(pr107467-2.C:23)
==13643== by 0x4011B2: other_func() (pr107467-2.C:40)
==13643== by 0x4011ED: main (pr107467-2.C:48)
So I guess it might be something in between DSE and aliasing info investigated
by IPA modref.
@Honza: Can you take a look?
next prev parent reply other threads:[~2022-12-28 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 22:10 [Bug translation/107467] New: " volker.weissmann at gmx dot de
2022-10-30 23:22 ` [Bug tree-optimization/107467] " pinskia at gcc dot gnu.org
2022-10-30 23:36 ` pinskia at gcc dot gnu.org
2022-10-30 23:38 ` [Bug tree-optimization/107467] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-30 23:39 ` pinskia at gcc dot gnu.org
2022-10-30 23:39 ` pinskia at gcc dot gnu.org
2022-11-05 10:29 ` rguenth at gcc dot gnu.org
2022-11-21 13:23 ` marxin at gcc dot gnu.org
2022-12-28 10:07 ` marxin at gcc dot gnu.org [this message]
2023-01-04 17:29 ` [Bug tree-optimization/107467] [12/13 Regression] Miscompilation involing -Os , -flto and -fno-strict-aliasing since r12-656-ga564da506f52be66 hubicka at gcc dot gnu.org
2023-01-13 11:47 ` rguenth at gcc dot gnu.org
2023-01-13 22:08 ` hubicka at ucw dot cz
2023-05-08 12:25 ` [Bug tree-optimization/107467] [12/13/14 " rguenth 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-107467-4-3Xj1O5XFhr@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).