Re: wined3d: print the architecture when showing driver problems
On 23 June 2013 07:10, Austin English <austinenglish(a)gmail.com> wrote:
Please consider applying before the release of 1.6. It has no functional changes, but would really help when diagnosing user problems.
This is not really a wined3d patch. That said, while I agree that printing the architecture would be useful here, you can probably avoid the #ifdef by using something along the lines of sizeof(void *) == 8 ? "64-bit" : "32-bit", although ideally we'd probably get the actual architecture from somewhere like ntdll.
On Mon, Jun 24, 2013 at 12:20 AM, Henri Verbeet <hverbeet(a)gmail.com> wrote:
On 23 June 2013 07:10, Austin English <austinenglish(a)gmail.com> wrote:
Please consider applying before the release of 1.6. It has no functional changes, but would really help when diagnosing user problems.
This is not really a wined3d patch. That said, while I agree that printing the architecture would be useful here, you can probably avoid the #ifdef by using something along the lines of sizeof(void *) == 8 ? "64-bit" : "32-bit", although ideally we'd probably get the actual architecture from somewhere like ntdll.
My understanding was that using the _WIN64 macro was preferred. I can certainly do that instead. How's this? -- -Austin
On 26 June 2013 03:53, Austin English <austinenglish(a)gmail.com> wrote:
My understanding was that using the _WIN64 macro was preferred. I can certainly do that instead. How's this?
I could probably live with that, though perhaps make it a helper function, and I'm not entirely sure this will print something meaningful on e.g. ARM. This is really a winex11 patch though, so it's more something for Alexandre.
participants (2)
-
Austin English -
Henri Verbeet