From: Paul Koning <paulkoning@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Richard Biener <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC] Introduce -finline-memset-loops
Date: Fri, 13 Jan 2023 21:12:59 -0500 [thread overview]
Message-ID: <5268E9F0-32BC-4BE3-8ADE-F7A430DBBCCA@comcast.net> (raw)
In-Reply-To: <or358dzxqu.fsf@lxoliva.fsfla.org>
> On Jan 13, 2023, at 8:54 PM, Alexandre Oliva via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> Hello, Richard,
>
> Thank you for the feedback.
>
> On Jan 12, 2023, Richard Biener <richard.guenther@gmail.com> wrote:
>
>> On Tue, Dec 27, 2022 at 5:12 AM Alexandre Oliva via Gcc-patches
>> <gcc-patches@gcc.gnu.org> wrote:
>
>>> This patch extends the memset expansion to start with a loop, so as to
>>> still take advantage of known alignment even with long lengths, but
>>> without necessarily adding store blocks for every power of two.
>
>> I wonder if that isn't better handled by targets via the setmem pattern,
>
> That was indeed where I started, but then I found myself duplicating the
> logic in try_store_by_multiple_pieces on a per-target basis.
>
> Target-specific code is great for tight optimizations, but the main
> purpose of this feature is not an optimization. AFAICT it actually
> slows things down in general (due to code growth, and to conservative
> assumptions about alignment),
I thought machinery like the memcpy patterns have as one of their benefits the ability to find the alignment of their operands and from that optimize things. So I don't understand why you'd say "conservative".
paul
next prev parent reply other threads:[~2023-01-14 2:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 4:02 Alexandre Oliva
2023-01-12 13:18 ` Richard Biener
2023-01-14 1:54 ` Alexandre Oliva
2023-01-14 2:12 ` Paul Koning [this message]
2023-01-14 3:21 ` Alexandre Oliva
2023-01-16 7:26 ` Richard Biener
2023-01-19 11:25 ` Alexandre Oliva
2023-01-19 11:58 ` Richard Biener
2023-06-02 10:11 ` Alexandre Oliva
2023-06-02 14:58 ` Fangrui Song
2023-06-23 2:23 ` Introduce -finline-stringops (was: Re: [RFC] Introduce -finline-memset-loops) Alexandre Oliva
2023-09-15 7:59 ` Introduce -finline-stringops Alexandre Oliva
2023-09-21 6:52 ` [PATCH v2] " Alexandre Oliva
2023-09-23 5:56 ` [PATCH v3] " Alexandre Oliva
2023-11-20 12:51 ` Alexandre Oliva
2023-11-20 13:49 ` Richard Biener
2023-12-11 18:43 ` Introduce -finline-stringops (was: Re: [RFC] Introduce -finline-memset-loops) Sam James
2023-12-12 1:42 ` Introduce -finline-stringops Alexandre Oliva
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=5268E9F0-32BC-4BE3-8ADE-F7A430DBBCCA@comcast.net \
--to=paulkoning@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@adacore.com \
--cc=richard.guenther@gmail.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).