From: Richard Guenther <rguenther@suse.de>
To: Sebastian Pop <sebpop@gmail.com>
Cc: gcc-patches@gcc.gnu.org, matz@suse.de
Subject: Re: [PATCH 3/4] Do not check whether memory references accessed in every iteration trap.
Date: Tue, 24 Aug 2010 10:26:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1008241159290.28912@zhemvz.fhfr.qr> (raw)
In-Reply-To: <AANLkTimVuT0gju=A7uFEx+vYbUvjTdyNwrVhKJvjOiYJ@mail.gmail.com>
On Wed, 18 Aug 2010, Sebastian Pop wrote:
> >> I will prepare the combined patch if you think that this is a better
> >> form.
> >
> > Yes, I like that better.
>
> I sent out the new combined patches.
> Ok for trunk after regstrap?
Now I just noticed that -ftree-loop-if-convert-memory-writes is long
for -ftree-loop-if-convert-stores. But I suppose it doesn't really
matter. The patches are ok (with or without changing the option
name - whatever you prefer).
Thanks,
Richard.
next prev parent reply other threads:[~2010-08-24 10:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 21:41 [PATCH 0/4] if-conversion of loops with conditionals containing memory writes Sebastian Pop
2010-07-08 21:41 ` [PATCH 2/4] Outline fold_or_predicates from add_to_predicate_list Sebastian Pop
2010-07-09 12:13 ` Richard Guenther
2010-07-09 16:43 ` Sebastian Pop
2010-07-09 17:04 ` Sebastian Pop
2010-07-09 18:25 ` Richard Guenther
2010-07-09 18:59 ` Sebastian Pop
2010-07-08 21:42 ` [PATCH 3/4] Do not check whether memory references accessed in every iteration trap Sebastian Pop
2010-08-13 9:41 ` Richard Guenther
2010-08-17 17:18 ` Sebastian Pop
2010-08-18 9:35 ` Richard Guenther
2010-08-18 17:10 ` Sebastian Pop
2010-08-18 19:05 ` Richard Guenther
2010-08-18 19:29 ` [PATCH 3/3] Speed-up ifcvt_memrefs_wont_trap caching previous results Sebastian Pop
2010-08-18 19:29 ` [PATCH 2/3] Do not check whether memory references accessed in every iteration trap Sebastian Pop
2010-08-18 19:31 ` [PATCH 1/3] Add flag -ftree-loop-if-convert-memory-writes Sebastian Pop
2010-08-18 19:32 ` [PATCH 3/4] Do not check whether memory references accessed in every iteration trap Sebastian Pop
2010-08-24 10:26 ` Richard Guenther [this message]
2010-08-24 15:47 ` Sebastian Pop
2010-08-24 16:31 ` Sebastian Pop
2010-09-20 7:44 ` Gerald Pfeifer
2010-07-08 21:42 ` [PATCH 1/4] Add flag -ftree-loop-if-convert-memory-writes Sebastian Pop
2010-08-13 8:58 ` Richard Guenther
2010-08-13 20:43 ` Sebastian Pop
2010-08-16 9:46 ` Richard Guenther
2010-08-13 22:12 ` Sebastian Pop
2010-08-16 9:46 ` Richard Guenther
2010-08-13 22:22 ` Sebastian Pop
2010-08-16 9:53 ` Richard Guenther
2010-07-08 21:42 ` [PATCH 4/4] Speed-up ifcvt_memrefs_wont_trap caching previous results Sebastian Pop
2010-08-13 9:02 ` Richard Guenther
2010-08-12 16:19 ` [PATCH 0/4] if-conversion of loops with conditionals containing memory writes Sebastian Pop
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=alpine.LNX.2.00.1008241159290.28912@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=sebpop@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).