From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] tree-optimization/111294 - backwards threader PHI costing
Date: Sun, 17 Sep 2023 11:50:12 -0600 [thread overview]
Message-ID: <465dfd68-af06-43bd-bcd7-6703b9afae2b@gmail.com> (raw)
In-Reply-To: <20230914132331.8D7613858CDA@sourceware.org>
On 9/14/23 07:23, Richard Biener via Gcc-patches wrote:
> This revives an earlier patch since the problematic code applying
> extra costs to PHIs in copied blocks we couldn't make any sense of
> prevents a required threading in this case. Instead of coming up
> with an artificial other costing the following simply removes the
> bits.
>
> As with all threading changes this requires a plethora of testsuite
> adjustments, but only the last three are unfortunate as is the
> libgomp team.c adjustment which is required to avoid a bogus -Werror
> diagnostic during bootstrap.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu.
>
> Any objections?
>
> Thanks,
> Richard.
>
> PR tree-optimization/111294
> gcc/
> * tree-ssa-threadbackward.cc (back_threader_profitability::m_name):
> Remove
> (back_threader::find_paths_to_names): Adjust.
> (back_threader::maybe_thread_block): Likewise.
> (back_threader_profitability::possibly_profitable_path_p): Remove
> code applying extra costs to copies PHIs.
>
> libgomp/
> * team.c (gomp_team_start): Guard gomp_alloca to avoid false
> positive alloc-size diagnostic.
>
> gcc/testsuite/
> * gcc.dg/tree-ssa/pr111294.c: New test.
> * gcc.dg/tree-ssa/phi_on_compare-4.c: Adjust.
> * gcc.dg/tree-ssa/pr59597.c: Likewise.
> * gcc.dg/tree-ssa/pr61839_2.c: Likewise.
> * gcc.dg/tree-ssa/ssa-sink-18.c: Likewise.
> * g++.dg/warn/Wstringop-overflow-4.C: XFAIL subtest on ilp32.
> * gcc.dg/uninit-pred-9_b.c: XFAIL subtest everywhere.
> * gcc.dg/vect/vect-117.c: Make scan for not Invalid sum
> conditional on lp64.
No objections. IIRC this was all to deal with a code explosion problem
seen on sparc. As long as tree-ssa/pr69196-1.c hasn't gone crazy we're OK.
jeff
next parent reply other threads:[~2023-09-17 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230914132331.8D7613858CDA@sourceware.org>
2023-09-17 17:50 ` Jeff Law [this message]
[not found] <20230914132321.E17B13858C2B@sourceware.org>
2023-09-18 7:14 ` Jakub Jelinek
2023-09-18 7:51 ` Richard Biener
2023-09-14 13:23 Richard Biener
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=465dfd68-af06-43bd-bcd7-6703b9afae2b@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).