From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79575] [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate
Date: Mon, 11 Aug 2014 18:42:44 +0000 [thread overview]
Message-ID: <bug-79575-502-XNJQLO5I6p@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79575-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1651 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79575
--- Comment #8 from Henri Verbeet <hverbeet@gmail.com> ---
(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 could also happen on any app, not just wine, if it
> unmasks exceptions before calling into mesa code).
It's perhaps important to point out that Wine isn't a single application as
such, and we don't have a lot of control over how individual applications setup
the FPU. The test in question exists because some applications expect us to
setup the FPU in a specific way, while others expect us to leave it alone.
Without having looked much into the llvm source for the backtrace, it's perhaps
also a bit odd that compiling a pass-through shader is doing anything involving
denormals in the first place.
> Though IIRC you aren't actually expected to leave the fpu control word in a
> non-standard state when you're calling into library code, so I'm not really
> sure if this qualifies as a mesa bug. In any way since this happens in llvm
> code finally here it might even be a bug there. I guess the only way to fix
Mostly just for reference, regressions every now and then aside, the Wine D3D
tests pretty much just pass with r600g / sb; that's currently my main
development setup. (And somewhat off-topic, but not entirely unrelated to this
bug, the reason that that's not a radeonsi system is because I think the llvm
dependency is just painful to work with.)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2591 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-08-11 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 7:56 [Bug 79575] New: [radeonsi] Wine's d3d8 test crashes in SITargetLowering::analyzeImmediate bugzilla-daemon
2014-08-08 1:36 ` [Bug 79575] " bugzilla-daemon
2014-08-08 2:55 ` bugzilla-daemon
2014-08-08 8:21 ` bugzilla-daemon
2014-08-08 19:29 ` bugzilla-daemon
2014-08-10 12:47 ` bugzilla-daemon
2014-08-11 2:01 ` bugzilla-daemon
2014-08-11 17:25 ` bugzilla-daemon
2014-08-11 18:42 ` bugzilla-daemon [this message]
2014-08-12 0:10 ` bugzilla-daemon
2014-08-12 23:21 ` bugzilla-daemon
2017-05-24 8:13 ` bugzilla-daemon
2017-05-24 8:36 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-79575-502-XNJQLO5I6p@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox