From: Aldy Hernandez <aldyh@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [trans-mem] avoid transforming already optimized memory variants
Date: Wed, 18 Nov 2009 12:53:00 -0000 [thread overview]
Message-ID: <20091118120150.GA4578@redhat.com> (raw)
In-Reply-To: <4B02CF9A.7050305@redhat.com>
> If you're going to do this, are you going to incorporate this knowledge
> into the optimization pass? Or is the fact that we already have an
> address instead of a memory too annoying?
Do you mean not accumulating any optimized stores/loads variants if
we're not going to (re)optimize them (tm_memopt_accumulate_memops)?
I suppose we should get tm_memopt_accumulate_memops() to use
is_tm_simple* to avoid doing unecessary work.
Perhaps we should avoid global memory optimizations altogether for functions
that have hand-coded RaR, RfW, etc?
next prev parent reply other threads:[~2009-11-18 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 15:25 Aldy Hernandez
2009-11-17 16:48 ` Richard Henderson
2009-11-18 12:53 ` Aldy Hernandez [this message]
2009-11-18 16:24 ` Richard Henderson
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=20091118120150.GA4578@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.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).