From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Richard Biener <rguenther@suse.de>,
Pat Haugen <pthaugen@linux.vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, wschmidt@linux.vnet.ibm.com
Subject: Re: [PATCH][v4] GIMPLE store merging pass
Date: Thu, 29 Sep 2016 08:24:00 -0000 [thread overview]
Message-ID: <57ECC8FE.3040602@foss.arm.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1609290934210.26629@t29.fhfr.qr>
On 29/09/16 08:36, Richard Biener wrote:
> On Wed, 28 Sep 2016, Pat Haugen wrote:
>
>> On 09/28/2016 10:54 AM, Kyrill Tkachov wrote:
>>> +fstore-merging
>>> +Common Var(flag_store_merging) Optimization
>>> +Use the tree store merging pass.
>>> +
>> Did you purposely leave off "Report" for this option? I noticed the option didn't show up in the "options enabled:" section of the .s file when -fverbose-asm is specified.
> Report should be added. Also please don't mention "tree" -- this is
> user facing documentation which shouldn't talk about GCC internals.
> Thus for example "Merge adjacent stores." would be more appropriate here.
Thanks, I'll update this.
Kyrill
> Richard.
next prev parent reply other threads:[~2016-09-29 7:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 16:00 Kyrill Tkachov
2016-09-28 16:07 ` Bill Schmidt
2016-09-28 16:09 ` Kyrill Tkachov
2016-09-29 16:01 ` Pat Haugen
2016-09-29 16:10 ` Kyrill Tkachov
2016-09-28 17:32 ` Pat Haugen
2016-09-29 8:02 ` Richard Biener
2016-09-29 8:24 ` Kyrill Tkachov [this message]
2016-09-29 10:54 ` Richard Biener
2016-09-29 15:37 ` Kyrill Tkachov
2016-09-30 7:09 ` Richard Biener
2016-09-30 15:25 ` Kyrill Tkachov
2016-09-30 15:34 ` Kyrill Tkachov
2016-09-30 17:02 ` Richard Biener
2016-09-30 16:58 ` Kyrill Tkachov
2016-10-04 8:18 ` Richard Biener
2016-10-03 13:02 ` Kyrill Tkachov
2016-10-03 16:43 ` Richard Biener
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=57ECC8FE.3040602@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pthaugen@linux.vnet.ibm.com \
--cc=rguenther@suse.de \
--cc=wschmidt@linux.vnet.ibm.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).