public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109154] [13 regression] jump threading de-optimizes nested floating point comparisons Date: Tue, 28 Mar 2023 12:18:08 +0000 [thread overview] Message-ID: <bug-109154-4-DXXKcrJNzz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109154-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The above slightly simplified (dead var removal, preprocessing etc.): typedef struct __attribute__((__packed__)) _Atom { float x, y, z; int type; } Atom; typedef struct __attribute__((__packed__)) _FFParams { int hbtype; float radius; float hphb; float elsc; } FFParams; void fasten_main (unsigned long group, unsigned long natlig, unsigned long natpro, const Atom *protein, const Atom *ligand, const FFParams *forcefield, float *energies) { float etot[64]; float lpos_x[64]; for (int l = 0; l < 64; l++) { etot[l] = 0.f; lpos_x[l] = 0.f; } for (int il = 0; il < natlig; il++) { const Atom l_atom = ligand[il]; const FFParams l_params = forcefield[l_atom.type]; for (int ip = 0; ip < natpro; ip++) { const Atom p_atom = protein[ip]; const FFParams p_params = forcefield[p_atom.type]; const float radij = p_params.radius + l_params.radius; const float elcdst = (p_params.hbtype == 70 && l_params.hbtype == 70) ? 4.0f : 2.0f; const float elcdst1 = (p_params.hbtype == 70 && l_params.hbtype == 70) ? 0.25f : 0.5f; const int type_E = ((p_params.hbtype == 69 || l_params.hbtype == 69)); const float chrg_init = l_params.elsc * p_params.elsc; for (int l = 0; l < 64; l++) { const float x = lpos_x[l] - p_atom.x; const float distij = (x * x); const float distbb = distij - radij; const int zone1 = (distbb < 0.0f); float chrg_e = chrg_init * ((zone1 ? 1.0f : (1.0f - distbb * elcdst1)) * (distbb < elcdst ? 1.0f : 0.0f)); float neg_chrg_e = -__builtin_fabsf(chrg_e); chrg_e = type_E ? neg_chrg_e : chrg_e; etot[l] += chrg_e * 45.0f; } } } for (int l = 0; l < 64; l++) energies[group * 64 + l] = etot[l] * 0.5f; } The r13-2266 to r13-2267 diff indeed starts during threadfull1, the dump says: ... Registering killing_def (path_oracle) distbb_75 - Registering value_relation (path_oracle) (iftmp.0_32 <= distbb_75) (root: bb16) -path: 16->18->xx REJECTED -Checking profitability of path (backwards): bb:18 (3 insns) bb:16 (6 insns) bb:23 - Control statement insns: 2 - Overall: 7 insns - - Registering killing_def (path_oracle) distbb_75 - Registering value_relation (path_oracle) (iftmp.0_32 <= distbb_75) (root: bb23) -path: 23->16->18->xx REJECTED -Checking profitability of path (backwards): bb:18 (3 insns) bb:16 (6 insns) bb:23 (3 insns) bb:15 - Control statement insns: 2 - Overall: 10 insns - FAIL: Did not thread around loop and would copy too many statements. -Checking profitability of path (backwards): bb:18 (3 insns) bb:16 (6 insns) bb:23 (3 insns) bb:22 (latch) - Control statement insns: 2 - Overall: 10 insns - FAIL: Did not thread around loop and would copy too many statements. +Checking profitability of path (backwards): + [10] Registering jump thread: (16, 18) incoming edge; (18, 20) nocopy; +path: 16->18->20 SUCCESS Checking profitability of path (backwards): bb:20 (7 insns) bb:18 Control statement insns: 2 Overall: 5 insns ... etc. Though, I know nothing about the threader and don't see suspect ranges in the decisions there.
next prev parent reply other threads:[~2023-03-28 12:18 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-16 11:57 [Bug tree-optimization/109154] New: [13 regression] aarch64 -mcpu=neoverse-v1 microbude performance regression pgodbole at nvidia dot com 2023-03-16 13:11 ` [Bug tree-optimization/109154] " tnfchris at gcc dot gnu.org 2023-03-16 14:58 ` [Bug target/109154] " rguenth at gcc dot gnu.org 2023-03-16 17:03 ` tnfchris at gcc dot gnu.org 2023-03-16 17:03 ` [Bug target/109154] [13 regression] jump threading with de-optimizes nested floating point comparisons tnfchris at gcc dot gnu.org 2023-03-22 10:20 ` [Bug tree-optimization/109154] [13 regression] jump threading " aldyh at gcc dot gnu.org 2023-03-22 10:29 ` avieira at gcc dot gnu.org 2023-03-22 12:22 ` rguenth at gcc dot gnu.org 2023-03-22 12:42 ` rguenth at gcc dot gnu.org 2023-03-22 13:11 ` aldyh at gcc dot gnu.org 2023-03-22 14:00 ` amacleod at redhat dot com 2023-03-22 14:39 ` aldyh at gcc dot gnu.org 2023-03-27 8:09 ` rguenth at gcc dot gnu.org 2023-03-27 9:30 ` jakub at gcc dot gnu.org 2023-03-27 9:42 ` aldyh at gcc dot gnu.org 2023-03-27 9:44 ` jakub at gcc dot gnu.org 2023-03-27 10:18 ` rguenther at suse dot de 2023-03-27 10:40 ` jakub at gcc dot gnu.org 2023-03-27 10:44 ` jakub at gcc dot gnu.org 2023-03-27 10:54 ` rguenth at gcc dot gnu.org 2023-03-27 10:56 ` jakub at gcc dot gnu.org 2023-03-27 10:59 ` jakub at gcc dot gnu.org 2023-03-27 17:07 ` jakub at gcc dot gnu.org 2023-03-28 8:33 ` rguenth at gcc dot gnu.org 2023-03-28 9:01 ` cvs-commit at gcc dot gnu.org 2023-03-28 10:07 ` tnfchris at gcc dot gnu.org 2023-03-28 10:08 ` tnfchris at gcc dot gnu.org 2023-03-28 12:18 ` jakub at gcc dot gnu.org [this message] 2023-03-28 12:25 ` rguenth at gcc dot gnu.org 2023-03-28 12:42 ` rguenth at gcc dot gnu.org 2023-03-28 13:19 ` rguenth at gcc dot gnu.org 2023-03-28 13:44 ` jakub at gcc dot gnu.org 2023-03-28 13:52 ` jakub at gcc dot gnu.org 2023-03-28 15:31 ` amacleod at redhat dot com 2023-03-28 15:40 ` jakub at gcc dot gnu.org 2023-03-28 15:53 ` amacleod at redhat dot com 2023-03-28 15:58 ` jakub at gcc dot gnu.org 2023-03-28 16:42 ` amacleod at redhat dot com 2023-03-28 21:12 ` amacleod at redhat dot com 2023-03-29 6:33 ` cvs-commit at gcc dot gnu.org 2023-03-29 6:38 ` rguenth at gcc dot gnu.org 2023-03-29 22:41 ` amacleod at redhat dot com 2023-03-30 18:17 ` cvs-commit at gcc dot gnu.org 2023-04-05 9:28 ` tnfchris at gcc dot gnu.org 2023-04-05 9:34 ` ktkachov at gcc dot gnu.org 2023-04-11 9:36 ` rguenth at gcc dot gnu.org 2023-04-13 16:54 ` jakub at gcc dot gnu.org 2023-04-13 17:25 ` rguenther at suse dot de 2023-04-13 17:29 ` jakub at gcc dot gnu.org 2023-04-14 18:10 ` jakub at gcc dot gnu.org 2023-04-14 18:14 ` jakub at gcc dot gnu.org 2023-04-14 18:22 ` jakub at gcc dot gnu.org 2023-04-14 19:09 ` jakub at gcc dot gnu.org 2023-04-15 10:10 ` cvs-commit at gcc dot gnu.org 2023-04-17 11:07 ` jakub at gcc dot gnu.org 2023-04-25 18:32 ` [Bug tree-optimization/109154] [13/14 " tnfchris at gcc dot gnu.org 2023-04-25 18:34 ` jakub at gcc dot gnu.org 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-04-26 9:43 ` tnfchris at gcc dot gnu.org 2023-04-26 10:07 ` jakub at gcc dot gnu.org 2023-07-07 18:10 ` tnfchris at gcc dot gnu.org 2023-07-10 7:15 ` rguenth at gcc dot gnu.org 2023-07-10 10:33 ` tnfchris at gcc dot gnu.org 2023-07-10 10:46 ` rguenth at gcc dot gnu.org 2023-07-10 11:02 ` tnfchris at gcc dot gnu.org 2023-07-10 11:27 ` rguenth at gcc dot gnu.org 2023-07-10 11:49 ` tnfchris at gcc dot gnu.org 2023-07-14 10:22 ` cvs-commit at gcc dot gnu.org 2023-07-14 10:22 ` cvs-commit at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2023-10-02 10:53 ` cvs-commit at gcc dot gnu.org 2023-10-18 8:54 ` cvs-commit at gcc dot gnu.org 2023-10-18 8:54 ` cvs-commit at gcc dot gnu.org 2023-10-18 8:54 ` cvs-commit at gcc dot gnu.org 2023-10-18 8:55 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:20 ` cvs-commit at gcc dot gnu.org 2023-11-09 14:25 ` [Bug tree-optimization/109154] [13 " tnfchris 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-109154-4-DXXKcrJNzz@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).