public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103227] [12 Regression] 58% exchange2 regression with -Ofast -march=native on zen3 since r12-5223-gecdf414bd89e6ba251f6b3f494407139b4dbae0e Date: Sun, 21 Nov 2021 15:16:28 +0000 [thread overview] Message-ID: <bug-103227-4-I5StbZL6JE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103227 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>: https://gcc.gnu.org/g:0f5afb626381d19bfced30bc19cf3b03867fa6f5 commit r12-5439-g0f5afb626381d19bfced30bc19cf3b03867fa6f5 Author: Jan Hubicka <jh@suse.cz> Date: Sun Nov 21 16:15:41 2021 +0100 Improve base tracking in ipa-modref on exchange2 benchamrk we miss some useful propagation because modref gives up very early on analyzing accesses through pointers. For example in int test (int *a) { int i; for (i=0; a[i];i++); return i+a[i]; } We are not able to determine that a[i] accesses are relative to a. This is because get_access requires the SSA name that is in MEM_REF to be PARM_DECL while on other places we use ipa-prop helper to work out the proper base pointers. This patch commonizes the code in get_access and parm_map_for_arg so both use the check properly and extends it to also figure out that newly allocated memory is not a side effect to caller. gcc/ChangeLog: 2021-11-21 Jan Hubicka <hubicka@ucw.cz> PR ipa/103227 * ipa-modref.c (parm_map_for_arg): Rename to ... (parm_map_for_ptr): .. this one; handle static chain and calls to malloc functions. (modref_access_analysis::get_access): Use parm_map_for_ptr. (modref_access_analysis::process_fnspec): Update. (modref_access_analysis::analyze_load): Update. (modref_access_analysis::analyze_store): Update. gcc/testsuite/ChangeLog: 2021-11-21 Jan Hubicka <hubicka@ucw.cz> PR ipa/103227 * gcc.dg/tree-ssa/modref-15.c: New test.
next prev parent reply other threads:[~2021-11-21 15:16 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-13 21:05 [Bug tree-optimization/103227] New: 58% exchange2 regression with -Ofast -march=native on zen3 between g:1ae8edf5f73ca5c3 and g:2af63f0f53a12a72 hubicka at gcc dot gnu.org 2021-11-13 22:00 ` [Bug ipa/103227] " hubicka at gcc dot gnu.org 2021-11-13 22:11 ` hubicka at gcc dot gnu.org 2021-11-13 22:15 ` hubicka at gcc dot gnu.org 2021-11-15 9:04 ` [Bug ipa/103227] [12 Regression] 58% exchange2 regression with -Ofast -march=native on zen3 since r12-5223-gecdf414bd89e6ba251f6b3f494407139b4dbae0e rguenth at gcc dot gnu.org 2021-11-19 18:18 ` jamborm at gcc dot gnu.org 2021-11-19 21:12 ` hubicka at kam dot mff.cuni.cz 2021-11-19 21:22 ` hubicka at gcc dot gnu.org 2021-11-19 23:21 ` jamborm at gcc dot gnu.org 2021-11-20 12:32 ` hubicka at kam dot mff.cuni.cz 2021-11-20 12:39 ` hubicka at kam dot mff.cuni.cz 2021-11-21 15:16 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-23 17:02 ` jamborm at gcc dot gnu.org 2021-11-24 12:52 ` jamborm at gcc dot gnu.org 2021-11-25 17:17 ` cvs-commit at gcc dot gnu.org 2021-11-26 9:19 ` hubicka at gcc dot gnu.org 2021-11-28 18:56 ` hubicka at gcc dot gnu.org 2022-12-14 0:04 ` cvs-commit at gcc dot gnu.org 2023-08-15 15:45 ` jamborm 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-103227-4-I5StbZL6JE@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).