| Subject: | Re: [trans-mem] avoid transforming already optimized memory variants |
|---|---|
| From: | Aldy Hernandez |
| Date: | Wed, 18 Nov 2009 08:01:51 -0400 |
> 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? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH, ARM] Misaligned access support for ARM Neon, Ira Rosen |
|---|---|
| Next by Date: | [PATCH, RFC?] Verify that VCE(SSA_NAME) does not occur on any LHS, Martin Jambor |
| Previous by Thread: | Re: [trans-mem] avoid transforming already optimized memory variants, Richard Henderson |
| Next by Thread: | Re: [trans-mem] avoid transforming already optimized memory variants, Richard Henderson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |