search for: nanoant

...tiums are SSE4.x only * I have marked HasAVX2 as "volatile", since otherwise it gets magically zeroed (by optimizer?) when compiling clang with latest clang build from trunk lib/Target/X86/X86Subtarget.cpp: * Also enabling X86::FeatureFastUAMem for Haswell Regards, -- Adam Strzelecki | nanoant.com | twitter.com/nanoant -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-detect-haswell.patch Type: application/octet-stream Size: 1765 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130912/b6842ec0/attachment.obj&...

On 17 Sep 2013, at 18:18, Mark Lacey <mark.lacey at apple.com> wrote: > This means that from build to build, depending on whether a Git change or SVN change is the most recent on my branch, I will get different results. That seems problematic. If you're not rebasing after pulling in changes from LLVM svn, then you're going to be in for a world of pain later (I, unfortunately,

Hi Adam, > * I have marked HasAVX2 as "volatile", since otherwise it gets > magically zeroed (by optimizer?) when compiling clang with latest > clang build from trunk That's far more worrying to me than not being able to detect Haswell. I can't reproduce the problem here at the moment: both debug and release builds give identical assembly for Host.cpp. I don't

...b/Support/Release/Host.o ; \ then /bin/mv -f "/tmp/llvm.q35LGwjHmR/lib/Support/Release/Host.d.tmp" "/tmp/llvm.q35LGwjHmR/lib/Support/Release/Host.d"; else /bin/rm "/tmp/llvm.q35LGwjHmR/lib/Support/Release/Host.d.tmp"; exit 1; fi Regards, -- Adam Strzelecki | nanoant.com | twitter.com/nanoant -------------- next part -------------- A non-text attachment was scrubbed... Name: Host-objects.tbz2 Type: application/octet-stream Size: 6366 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130912/6c851eb1/attachment.obj> ---...