|
|
#1 | |
|
Registered User
|
As in title, it seems that starting with the 185 series, the driver produces NaN on /0. This is causing issues with wine applications:
http://bugs.winehq.org/show_bug.cgi?id=20053 Is this intentional behavior? Should this be considered something to be fixed/handled in wine's d3d layer, or an nvidia bug? Last edited by Nephyrin; 09-15-09 at 01:12 PM. Reason: typo |
|
|
|
|
|
|
#2 | |
|
Null Byte Bug Hunter
Join Date: Mar 2007
Location: N 49 52'19", E 8 38'17", Germany
Posts: 79
|
This is defined in IEEE 754 and not a matter of interpretation so I would say the Nvidia driver is (now) correct.
__________________
GA-EX38-DS5 | Core 2 Q9450 | AC Freezer 7 Pro | 2x KVR800D2E5/2G | ZOTAC GeForce 8800GT AMP! 4x HDP725032GLA360 RAID-10 | Enermax PRO82+ 525W | CoolerMaster RC-590 GA-EX58-UD5 | Core i 7-940 | CoolerMaster V8 | KHX12800D3LLK3/6GX | ZOTAC GeForce GTX 280 4x WD10EADS RAID-10 | Enermax REVOLUTION85+ 850W | CoolerMaster RC-600 ZOTAC GeForce 9300-ITX WiFi | Celeron E3200 | 2x KVR800D2E5/2G | SSDSA2MH160G2 ![]() WD10EADS | GGC-H20L | Enermax PRO82+ 385W | Lian Li PC-Q07B | Boy this box is cramped |
|
|
|
|
![]() |
| Thread Tools | |
|
|