Why not just look for the AVX registers by name that are only available if they are correctly detected by the native lldb-server or debugserver? Then we can avoid all of this. If we don't execute any instructions that crash the program, we can stop before any specialized AVX instructions are executed and kill the program is we don't see a register by name?
> On Jan 12, 2018, at 8:44 AM, Jason Molenda via Phabricator via lldb-commits > <lldb-commits@lists.llvm.org> wrote: > > jasonmolenda added a comment. > > I suppose a possible alternative would be to figure out the avx2 / avx512 > features manually based on the cpuid instead of letting the compiler do it > for us. e.g. > https://stackoverflow.com/questions/1666093/cpuid-implementations-in-c and > then checking the bits as e.g. described in > https://en.wikipedia.org/wiki/CPUID . Bummer to do it so low level if we can > delegate this to the compiler though. > > > Repository: > rL LLVM > > https://reviews.llvm.org/D41962 > > > > _______________________________________________ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
