From: Alexandre Oliva <oliva@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>,
GCC Patches <gcc-patches@gcc.gnu.org>, Zdenek Dvorak <ook@ucw.cz>
Subject: Re: [RFC] test builtin ratio for loop distribution
Date: Tue, 16 Feb 2021 07:47:54 -0300 [thread overview]
Message-ID: <ora6s4s2zp.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orblcktxub.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Tue, 16 Feb 2021 01:56:12 -0300")
On Feb 16, 2021, Alexandre Oliva <oliva@adacore.com> wrote:
>> So I wonder whether we should instead re-run CCP after loop opts which
>> computes nonzero bits as well instead of the above "hack".
That works. It takes care of both the dest alignment and the len ctz.
Explicitly masking out the len tz from nonzero bits also works, but I
suppose the ccp pass does a better job, and it takes care of memcpy and
memmove as well.
I noticed that ccp releases CDI_DOMINATORS information. It looks like
the last copy_prop pass, now replaced with ccp in my tree, was late
enough that it doesn't seem to matter, but at first I thought you meant
an earlier copy_prop, that runs before graphite, and dropping dominator
info at that point was a problem for e.g. cunroll.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Vim, Vi, Voltei pro Emacs -- GNUlius Caesar
next prev parent reply other threads:[~2021-02-16 10:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 12:40 Alexandre Oliva
2021-01-27 15:12 ` Richard Biener
2021-01-28 5:28 ` Alexandre Oliva
2021-01-28 8:59 ` Richard Biener
2021-02-02 17:13 ` Alexandre Oliva
2021-02-03 8:59 ` Richard Biener
2021-02-03 15:11 ` Alexandre Oliva
2021-02-04 8:37 ` Richard Biener
2021-02-04 22:17 ` Alexandre Oliva
2021-02-05 8:02 ` Richard Biener
2021-02-11 10:19 ` Alexandre Oliva
2021-02-11 12:14 ` Alexandre Oliva
2021-02-12 11:34 ` Richard Biener
2021-02-16 4:56 ` Alexandre Oliva
2021-02-16 10:47 ` Alexandre Oliva [this message]
2021-02-16 12:11 ` Richard Biener
2021-02-19 8:08 ` [PR94092] " Alexandre Oliva
2021-02-22 9:53 ` Richard Biener
2021-04-29 4:26 ` Alexandre Oliva
2021-04-30 14:42 ` Jeff Law
2021-05-03 8:55 ` Richard Biener
2021-05-04 1:59 ` Alexandre Oliva
2021-05-04 5:49 ` Prathamesh Kulkarni
2021-05-04 6:09 ` Alexandre Oliva
2021-02-05 0:13 ` Jim Wilson
2021-02-11 10:11 ` 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=ora6s4s2zp.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=ook@ucw.cz \
--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).