search for: x86utils

...AVX properly. I had hoped to avoid these kinds of changes as much as possible. I would prefer to create a new library. Is that a reasonable solution? If so, is there are good name for it? I can imagine more code that just shuffle decode logic might go in there eventually. Maybe something like X86Utils.a would be a good name. -Dave

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort