From: Sandra Loosemore <sandra.loosemore@siemens.com>
To: Tobias Burnus <tobias@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] [OpenMP] GC unused SIMD clones
Date: Tue, 3 Jan 2023 21:47:02 -0700 [thread overview]
Message-ID: <47206b92-dc53-dc81-16ca-38cae5baee6f@siemens.com> (raw)
In-Reply-To: <dee787c7-ad85-543f-4de8-f8aaecf5d047@codesourcery.com>
On 1/2/23 03:20, Tobias Burnus wrote:
> On 25.11.22 03:13, Sandra Loosemore wrote:
>> This patch is a followup to my not-yet-reviewed patch
>> [PATCH v4] OpenMP: Generate SIMD clones for functions with "declare
>> target"
>
> That patch got reviewed and went into mainline on Nov 15, 2022 as
> https://gcc.gnu.org/r13-4309-g309e2d95e3b930c6f15c8a5346b913158404c76d>>
>
>> In comments on a previous iteration of that patch, I was asked to do
>> something to delete unused SIMD clones to avoid code bloat; this is it.
>>
>> I've implemented something like a simple mark-and-sweep algorithm.
>> Clones that are used are marked at the point where the call is
>> generated in the vectorizer. The loop that iterates over functions to
>> apply the passes after IPA is modified to defer processing of unmarked
>> clones, and anything left over is deleted.
>
>
> Jakub referred to Honza for the review, who wrote yesterday off list (to
> me and Sandra):
>
>> I am really sorry for taking so long time. It was busy month for me
>> and I was not very keen about the idea, since we had such logic
>> implemented many years ago but removed it to be able to determine
>> functions to be output early and optimize code layout.
>>
>> I see that this is not possible with current organization where
>> vectorization is run late, so I guess it does make sense to do what you
>> are doing.
>>
>> Patch is OK,
>> Honza
>
> Thanks for the review! (And to Sandra: thanks for the patch.)
>
> I leave it to Sandra to commit her patch and only want to update the
> gcc-patches@ email. However. I think we can expect a commit tomorrow.
> (Today is a holiday at her place - as new year's day fell on a Sunday.)
Yes, the patch is committed now, and also backported to og12. Thanks,
Honza, for the review, and Tobias, for your assistance. I'm really glad
to get this project done, finally. :-)
-Sandra
prev parent reply other threads:[~2023-01-04 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 2:13 Sandra Loosemore
2022-12-02 16:17 ` Jakub Jelinek
2023-01-02 10:20 ` Tobias Burnus
2023-01-04 4:47 ` Sandra Loosemore [this message]
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=47206b92-dc53-dc81-16ca-38cae5baee6f@siemens.com \
--to=sandra.loosemore@siemens.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=sandra@codesourcery.com \
--cc=tobias@codesourcery.com \
/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).