Xeons certainly support SSE (or AVX if they are new enough). You did however mention this was using some production server, which to me means it's probably using some old windows version missing some updates. In particular, windows 7 (don't ask me to what server version this corresponds) without some patches doesn't support avx (the same is true for 32bit windows xp and sse). And yes, llvm and also at some point in mesa there were issues detecting this correctly (that is if the cpu supported it but the OS did not). There were also problems communicating that correctly from mesa to llvm (as the interface changed several times, in particular llvm would still use some cpu features it thinks are possible to use even if we figured we don't want to use them, since llvm used its own autodetection depending on llvm version anyway). I believe though these issues should all be fixed in mesa, we're now more explicitly telling llvm to not use avx/avx2 if we don't detect support for it. Albeit I wouldn't quite be sure that this really works now with all llvm versions - if you're interested in how this works from the mesa side look at lp_build_create_jit_compiler_for_module() where we tell llvm which features it should use (and what kind of cpu this is), there's also several llvm bugs quoted there (I think they should be all fixed with 3.6 at least).
Not sure about the linking issues... Roland Am 21.03.2016 um 02:02 schrieb Jason Anderssen: > Hi All, > > I thought I would share for the benefits of anyone in a similar issue like > me one day. > I think the cause is the processors being used are xeon, and they don¹t > support sse extensions. > I thought maybe the 3.4 version of LLVM must have a bug in detecting this > processor, so I tried 3.6.2 of LLVM, and it all works now. (I read through > forums, and notice 3.7 had some processors bug detection issues, and 3.8 > would not link with MESA for me:( ) > So since I feel my outcome is correct, does anyone have a ŒMESA¹ > recommended way to fix this, I see that on the Mesa site, the recommended > LVM is 3.4, however this obviously won¹t suffice, so this is the reason I > ask simply for a recommended combination I should be using. > > I tried LLVM 3.8 and the latest Mesa, but I get some really weird linkage > issues, happy to go back and try further with this if necessary? > > Cheers > Jason > > On 17/03/2016 12:36 pm, "Jason Anderssen" <janders...@exactal.com> wrote: > >> Mesa version is 11.1.2 >> LVM - 3.4 >> Ill see what I can do regarding a gdb backtrace. >> >> Cheers >> Jason >> >> On 17/03/2016 11:38 am, "Roland Scheidegger" <srol...@vmware.com> wrote: >> >>> Am 17.03.2016 um 01:52 schrieb Jason Anderssen: >>>> Hi all, >>>> >>>> I was wondering if anyone knows of or has seen a crash when Mesa is >>>> compiled for with LVM Pipe ? >>>> The reason I ask is that if our user uses a compiled version of Mesa >>>> using the slower software render, it works fine, the moment we compile >>>> it with LVM, it crashes. >>>> I have an api trace that shows how far it got, and a dump file if this >>>> would be of assistance? >>>> Also, it is only this one server that exhibits this problem from what >>>> we >>>> have been able to discover, however it is a pretty vanilla install as >>>> it >>>> is a production server, it is also running Terminal Services, so it is >>>> quite tightly controlled in regards to what gets installed. >>>> >>>> Thanks for your help in advance. >>>> >>>> Cheers >>>> Jason Anderssen >>>> >>> A gdb backtrace would probably be more useful. Also, what version of >>> mesa? >>> >>> Roland >>> >>> >> > > Internet Email Confidentiality Footer: This email and any files transmitted > with it contain privileged/confidential information intended for the > addressee. Neither the confidentiality of nor any privilege in the email is > waived, lost or destroyed by reason that it has been transmitted other than > to the addressee. If you are not the addressee indicated in this message (or > responsible for delivery of the message to such person), you may not copy or > deliver this message to anyone. In such case, you should destroy this > message, and notify us immediately. > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
