search for: somethinmg

...quot; order of the TableGen code as the movement is from the beginning of X86InstrSSE.td to the end of X86InstrFragmentsSIMD.td which is included immediately before X86InstrSSE.td. The failing tests aren't even looking for SSE code. I don't see how this patch could cause any failures. Is somethinmg tricky going on with the Frontend* tests at the moment? -Dave

On Jul 12, 2010, at 11:45 AM, David A. Greene wrote: > > I don't see how this patch could cause any failures. > > Is somethinmg tricky going on with the Frontend* tests at the moment? I just updated and ran everything and it's working fine for me. (Note that I haven't tested with your patch.) -eric

Hi David, On Fri, Jul 9, 2010 at 3:25 PM, David Greene <dag at cray.com> wrote: > Now that Bruno is putting in some AVX stuff, it's a good motivator to > move my x86 SIMD reorg work into trunk (and got management to agree to > prioritize it - Thanks Bruno! :) ). > > Attached is the first patch of many to accomplish this.  The overall > goal is to have all x86 SIMD

Now that Bruno is putting in some AVX stuff, it's a good motivator to move my x86 SIMD reorg work into trunk (and got management to agree to prioritize it - Thanks Bruno! :) ). Attached is the first patch of many to accomplish this. The overall goal is to have all x86 SIMD instructions share a set of common patterns so that we can have a more maintainable machine description (e.g. SS, SD,