<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 and mesa 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92214#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 and mesa 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92214">bug 92214</a> from <a class="email" href="mailto:mister.freeman@laposte.net" title="Barto <mister.freeman@laposte.net>"> Barto</a> <pre>Craig Tooper has made a suggestion who solves the problem : the idea is to "remove" the unsupported CPU features, by adding "-sse4.1" in MAttrs object when "util_cpu_caps.has_sse4_1 == false", so if I add this to Jose's patch the bug is solved : + if (!util_cpu_caps.has_sse4_1) { +#if HAVE_LLVM >= 0x0304 + MAttrs.push_back("-sse4.1"); +#else + MAttrs.push_back("-sse41"); +#endif + } this logic is not really natural for a developper who wants to use llvm lib, this developper would think that llvm will never use an unsupported cpu feature if this developper only passes good cpu features to the compiler, it seems that llvm will try to use by himself SSE4.1 even if the developper didn't add explicitely "+sse4.1" in his source code, we have this problem because llvm 3.7.0 treats pentium dual core cpu as "penryn" cpu, "penryn" supports SSE4 but not pentium dual core, in my logic llvm should be more stric, rigorous when he tries to associate a cpu with a cpu name, a cpu name should reflect exactly the cpu features, maybe a better solution would be to create a new cpu name in llvm source code, a cpu name who targets only cpu family 6 model 23 : "dualcore" in order to avoid this SSE4 problem, but I am not a llvm specialist</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>