From: "Wang, Hongyu" <hongyu.wang@intel.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH V2] Enable small loop unrolling for O2
Date: Fri, 11 Nov 2022 02:04:45 +0000 [thread overview]
Message-ID: <DM6PR11MB3306A4ED30A3D111153A7DD5FC009@DM6PR11MB3306.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGWvnymYBjT57TaCCf9SFcu6c+XxGyXPSdu_TYJKLjtE7xwa1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Thanks for the notification! I’m not aware of the compile farm before. Will see what’s the impact of my patch then.
Regards,
Hongyu, Wang
From: David Edelsohn <dje.gcc@gmail.com>
Sent: Thursday, November 10, 2022 1:22 AM
To: Wang, Hongyu <hongyu.wang@intel.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH V2] Enable small loop unrolling for O2
> This patch does not change rs6000/s390 since I don't have machines to
> test them, but I suppose the default behavior is the same since they
> enable flag_unroll_loops at O2.
There are Power (rs6000) systems in the Compile Farm.
Trial Linux on Z (s390x) VMs are available through the Linux Community Cloud.
https://linuxone.cloud.marist.edu/#/register?flag=VM
Thanks, David
next prev parent reply other threads:[~2022-11-11 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:22 David Edelsohn
2022-11-11 2:04 ` Wang, Hongyu [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-02 3:37 Hongyu Wang
2022-11-07 14:24 ` Richard Biener
2022-11-08 3:07 ` Hongtao Liu
2022-11-09 1:24 ` Hongyu Wang
2022-11-14 1:35 ` Hongtao Liu
2022-11-14 5:32 ` Hongyu Wang
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=DM6PR11MB3306A4ED30A3D111153A7DD5FC009@DM6PR11MB3306.namprd11.prod.outlook.com \
--to=hongyu.wang@intel.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).