[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 Samuel Pitoiset changed: What|Removed |Added Resolution|FIXED |WONTFIX

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 Samuel Pitoiset changed: What|Removed |Added Resolution|--- |FIXED

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #10 from Roland Scheidegger --- (In reply to comment #8) > (In reply to comment #7) > > Looks like this is happening purely for testing if a fpu control word would > > be preserved, the actual value used by d3d does disable them just

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #9 from Andrei Slavoiu --- Created attachment 104462 --> https://bugs.freedesktop.org/attachment.cgi?id=104462=edit r600_debug_ps.log Output when ran with R600_DEBUG=ps -- You are receiving this mail because: You are the

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #8 from Henri Verbeet --- (In reply to comment #7) > Looks like this is happening purely for testing if a fpu control word would > be preserved, the actual value used by d3d does disable them just fine > (though, of course, this

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #7 from Roland Scheidegger --- Specifically it looks like the wine test actually tries a control word which enables all fpu exceptions. Seems like nvidia drivers had the same problem at some point:

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #6 from Michel D?nzer --- (In reply to comment #5) > I tried adding R600_DEBUG=fs but no extra info was printed. That should be R600_DEBUG=ps for the pixel/fragment shader (you can see a list of supported debugging options with

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #5 from Andrei Slavoiu --- BTW, I just noticed that in the latest backtrace util_make_vertex_passthrough_shader_with_so no longer appears. Instead it starts from util_make_empty_fragment_shader. I tried adding R600_DEBUG=fs but no

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #4 from Andrei Slavoiu --- Created attachment 104309 --> https://bugs.freedesktop.org/attachment.cgi?id=104309=edit r600_debug_vs.log Log file with R600_DEBUG=vs -- You are receiving this mail because: You are the assignee for

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #3 from Henri Verbeet --- For what it's worth, test_fpu_setup() tests creating a D3D device with a custom FPU control word. (The background on that is that creating a D3D device should setup the FPU in a specific way, depending on if

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #2 from Michel D?nzer --- (In reply to comment #1) > Can you post the output of R600_DEBUG=cs ? Make that R600_DEBUG=vs , since the crash occurs in util_make_vertex_passthrough_shader_with_so(). -- You are receiving this mail

[Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate

https://bugs.freedesktop.org/show_bug.cgi?id=79575 --- Comment #1 from Tom Stellard --- Can you post the output of R600_DEBUG=cs ? -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: