public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/111157] [14 Regression] 416.gamess fails with a run-time abort when compiled with -O2 -flto after r14-3226-gd073e2d75d9ed4 Date: Fri, 25 Aug 2023 17:14:32 +0000 [thread overview] Message-ID: <bug-111157-4-2d5aEwZVES@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111157-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111157 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2023-08-25 --- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> --- With the propagation, PRE performs the following: void point.constprop.isra (double ISRA.1740, int & restrict ipoint, double & restrict x, double & restrict y, double & restrict z, int & restrict istat) { int iy; int ix; double & restrict prploc; int _5; - int _9; int _11; int _12; long int _13; @@ -13284,7 +15377,6 @@ <bb 2> [local count: 1073741824]: # DEBUG D#556 s=> prploc # DEBUG prploc => D#556 - *istat_1(D) = 0; if (ISRA.1740_70(D) != 6.08805302369215843745180305174265706886482420102590225625e-154) goto <bb 7>; [50.00%] else @@ -13301,8 +15393,7 @@ calcom (x_6(D), y_7(D), z_8(D)); <bb 5> [local count: 536870912]: - _9 = *ipoint_4(D); - if (_9 > 1) + if (_5 > 1) goto <bb 6>; [59.00%] else goto <bb 25>; [41.00%] The write of zero to where we know there is already zero is however problematic because all callers expect the pointed to value to be overwritten and dse2 pass does: @@ -20229,7 +14076,6 @@ xpt = 0.0; ypt = 0.0; zpt = 0.0; - istat = 0; point.constprop.isra (_73, &ipoint, &xpt, &ypt, &zpt, &istat); _77 = istat; if (_77 < 0) So I guess this is a nasty interaction with IPA-modref, and indeed -fno-ipa-modref avoids the issue. I'll discuss with Honza whether IPA-modref can be modified to kill the known values in summaries in such cases or whether it is IPA-CP that should avoid "knowing" the value.
next prev parent reply other threads:[~2023-08-25 17:14 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-25 14:30 [Bug ipa/111157] New: " jamborm at gcc dot gnu.org 2023-08-25 15:57 ` [Bug ipa/111157] [14 Regression] " pinskia at gcc dot gnu.org 2023-08-25 16:46 ` jamborm at gcc dot gnu.org 2023-08-25 17:14 ` jamborm at gcc dot gnu.org [this message] 2023-08-25 20:07 ` jamborm at gcc dot gnu.org 2023-08-26 11:50 ` hubicka at gcc dot gnu.org 2023-08-28 7:18 ` rguenth at gcc dot gnu.org 2023-08-28 12:12 ` jamborm at gcc dot gnu.org 2023-08-28 12:16 ` jamborm at gcc dot gnu.org 2023-08-29 11:32 ` hubicka at ucw dot cz 2023-10-05 12:22 ` jamborm at gcc dot gnu.org 2023-10-17 12:28 ` rguenth at gcc dot gnu.org 2023-10-30 17:38 ` cvs-commit at gcc dot gnu.org 2023-10-30 17:38 ` cvs-commit at gcc dot gnu.org 2023-10-30 17:41 ` jamborm at gcc dot gnu.org 2023-10-31 7:43 ` 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-111157-4-2d5aEwZVES@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).