[PATCH] D26242: Test for YMMRegisters.

Adrian Prantl via llvm-commits llvm-commits at lists.llvm.org
Mon Jan 8 08:51:38 PST 2018


"i386" not very helpful :-(

> On Jan 8, 2018, at 8:41 AM, Zachary Turner <zturner at google.com> wrote:
> 
> What does platform.processor() return? Is it possible to use that to detect the existence of avx and just disable the test?
> On Mon, Jan 8, 2018 at 8:36 AM Greg Clayton via Phabricator <reviews at reviews.llvm.org <mailto:reviews at reviews.llvm.org>> wrote:
> clayborg added a comment.
> Herald added a subscriber: llvm-commits.
> 
> Detecting x86_64h might be tricky on different platforms. Two things I can think of: explicitly compile using x86_64h and when you try to run it it might fail. I believe that will work for Darwin, but not sure about other OSs (linux, Android). Mach-o has the x86_64h CPU type/subtyype, but I am not sure how ELF does this since they only really have the machine type and it isn't enough to represent x86_64h. The other way would be to start up the process (if it launches on all platforms) and look for a register by name that is only available if haswell support is available on the system. I believe all of our targets do correctly detect their AVX regs, so just stopping and looking for the register by name, and end the test as an expected failure or success if the register isn't available.
> 
> 
> Repository:
>   rL LLVM
> 
> https://reviews.llvm.org/D26242 <https://reviews.llvm.org/D26242>
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20180108/b55f2919/attachment.html>


More information about the llvm-commits mailing list