From: Richard Biener <richard.guenther@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Alexandre Oliva <oliva@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>, Zdenek Dvorak <ook@ucw.cz>
Subject: Re: [PR94092] Re: [RFC] test builtin ratio for loop distribution
Date: Mon, 3 May 2021 10:55:27 +0200 [thread overview]
Message-ID: <CAFiYyc2O3QzfYdnOt+5kebkEoKLT2SrPZgi7VkKFs2QCdS0pOA@mail.gmail.com> (raw)
In-Reply-To: <a4bdbd11-5705-b120-55ed-024641a5c908@gmail.com>
On Fri, Apr 30, 2021 at 4:42 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
> On 4/28/2021 10:26 PM, Alexandre Oliva wrote:
> > On Feb 22, 2021, Richard Biener <richard.guenther@gmail.com> wrote:
> >
> >> On Fri, Feb 19, 2021 at 9:08 AM Alexandre Oliva <oliva@adacore.com> wrote:
> >>> Here's an improved version of the patch. Regstrapped on
> >>> x86_64-linux-gnu, with and without a patchlet that moved multi-pieces
> >>> ahead of setmem, and also tested with riscv32-elf.
> >>>
> >>> Is it ok to install? Or should it wait for stage1?
> >> It generally looks OK but I'd wait for stage1.
> > 'k, I've retested the patch now, and it's still working as expected.
>
> Then I'd go forward with it at this point.
Yes, it looks good to me as well.
Thanks,
Richard.
>
>
> >
> > I've dropped references to PR94092, since it's a different issue.
>
> ACK. Note I just put a patch into pr94092 that may be of interest. In
> simplest terms it tries to use REGNO_POINTER_ALIGN to increase the
> alignment of MEMs. We'd been using it internally for a bit before we
> went a slightly different direction. Feel free to use it if it's helpful.
>
>
> jeff
>
next prev parent reply other threads:[~2021-05-03 8:55 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
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 [this message]
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=CAFiYyc2O3QzfYdnOt+5kebkEoKLT2SrPZgi7VkKFs2QCdS0pOA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jeffreyalaw@gmail.com \
--cc=oliva@adacore.com \
--cc=ook@ucw.cz \
/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).