May 2016 - Wine-Devel - list.winehq.org

Re: include: Fix a typo in IDirect3D9Ex method

by Henri Verbeet

On 22 May 2016 at 14:30, Andrey Gusev <andrey.goosev(a)gmail.com> wrote: > - STDMETHOD(GetAdapterLUID)(THIS_ UINT Adatper, LUID *pLUID) PURE; > + STDMETHOD(GetAdapterLUID)(THIS_ UINT Adapter, LUID *pLUID) PURE; If you're touching it anyway, "Adapter" => "adapter" and "pLUID" => "luid".

May 22, 2016

Re: [PATCH 12/12] wined3d: Use ARB_fragment_coord_conventions for vpos fixups when supported.

by Henri Verbeet

On 20 May 2016 at 19:56, Matteo Bruni <mbruni(a)codeweavers.com> wrote: > if (reg_maps->vpos) > { > - if (shader->device->wined3d->flags & WINED3D_PIXEL_CENTER_INTEGER) > + if (gl_info->supported[ARB_FRAGMENT_COORD_CONVENTIONS]) > + shader_addline(buffer, "vpos = gl_FragCoord;\n"); > + else if (shader->device->wined3d->flags & WINED3D_PIXEL_CENTER_INTEGER) Isn't it harder than that? You're dropping the y-flip completely now. I think we can actually do that regardless of ARB_fragment_coord_conventions if we have always_offscreen, but not in general. It does look like the benefits of ARB_fragment_coord_conventions are somewhat limited. I probably mixed it up with ARB_clip_control when I initially suggested it. I think that would allow us to get rid of the position fixup, but we'd have to make it a requirement for shader model 4 if we wanted to avoid patch 6/12.

May 22, 2016

Re: [PATCH v2 09/12] d3d10core/tests: Add a geometry shader test.

by Henri Verbeet

On 20 May 2016 at 19:56, Matteo Bruni <mbruni(a)codeweavers.com> wrote: > +#if 0 > +struct gs_data > +{ > + float4 pos : SV_POSITION; > + float4 color : COLOR; > +}; > + > +[maxvertexcount(4)] > +void main(point struct gs_data vin[1], inout TriangleStream<gs_data> vout) > +{ > + float offset = 0.2 * vin[0].pos.w; > + gs_data v; > + > + v.color = vin[0].color; > + > + v.pos = float4(vin[0].pos.x - offset, vin[0].pos.y - offset, vin[0].pos.z, 1.0); > + vout.Append(v); > + v.pos = float4(vin[0].pos.x - offset, vin[0].pos.y + offset, vin[0].pos.z, 1.0); > + vout.Append(v); > + v.pos = float4(vin[0].pos.x + offset, vin[0].pos.y - offset, vin[0].pos.z, 1.0); > + vout.Append(v); > + v.pos = float4(vin[0].pos.x + offset, vin[0].pos.y + offset, vin[0].pos.z, 1.0); > + vout.Append(v); > +} > +#endif > + static const DWORD gs_code[] = > + { > + 0x43425844, 0x5c14d638, 0x1089a334, 0x4103d097, 0x218e3173, 0x00000001, 0x00000428, 0x00000005, > + 0x00000034, 0x0000008c, 0x000000e0, 0x00000134, 0x000003ac, 0x46454452, 0x00000050, 0x00000000, > + 0x00000000, 0x00000000, 0x0000001c, 0x47530400, 0x00000100, 0x0000001c, 0x7263694d, 0x666f736f, > + 0x52282074, 0x4c482029, 0x53204c53, 0x65646168, 0x6f432072, 0x6c69706d, 0x31207265, 0x2e302e30, > + 0x31303031, 0x36312e31, 0x00343833, 0x4e475349, 0x0000004c, 0x00000002, 0x00000008, 0x00000038, > + 0x00000000, 0x00000001, 0x00000003, 0x00000000, 0x00000f0f, 0x00000044, 0x00000000, 0x00000000, > + 0x00000003, 0x00000001, 0x00000f0f, 0x505f5653, 0x5449534f, 0x004e4f49, 0x4f4c4f43, 0xabab0052, > + 0x4e47534f, 0x0000004c, 0x00000002, 0x00000008, 0x00000038, 0x00000000, 0x00000001, 0x00000003, > + 0x00000000, 0x0000000f, 0x00000044, 0x00000000, 0x00000000, 0x00000003, 0x00000001, 0x0000000f, > + 0x505f5653, 0x5449534f, 0x004e4f49, 0x4f4c4f43, 0xabab0052, 0x52444853, 0x00000270, 0x00020040, > + 0x0000009c, 0x05000061, 0x002010f2, 0x00000001, 0x00000000, 0x00000001, 0x0400005f, 0x002010f2, > + 0x00000001, 0x00000001, 0x02000068, 0x00000001, 0x0100085d, 0x0100285c, 0x04000067, 0x001020f2, > + 0x00000000, 0x00000001, 0x03000065, 0x001020f2, 0x00000001, 0x0200005e, 0x00000004, 0x0f000032, > + 0x00100032, 0x00000000, 0x80201ff6, 0x00000041, 0x00000000, 0x00000000, 0x00004002, 0x3e4ccccd, > + 0x3e4ccccd, 0x00000000, 0x00000000, 0x00201046, 0x00000000, 0x00000000, 0x05000036, 0x00102032, > + 0x00000000, 0x00100046, 0x00000000, 0x06000036, 0x00102042, 0x00000000, 0x0020102a, 0x00000000, > + 0x00000000, 0x05000036, 0x00102082, 0x00000000, 0x00004001, 0x3f800000, 0x06000036, 0x001020f2, > + 0x00000001, 0x00201e46, 0x00000000, 0x00000001, 0x01000013, 0x05000036, 0x00102012, 0x00000000, > + 0x0010000a, 0x00000000, 0x0e000032, 0x00100052, 0x00000000, 0x00201ff6, 0x00000000, 0x00000000, > + 0x00004002, 0x3e4ccccd, 0x00000000, 0x3e4ccccd, 0x00000000, 0x00201106, 0x00000000, 0x00000000, > + 0x05000036, 0x00102022, 0x00000000, 0x0010002a, 0x00000000, 0x06000036, 0x00102042, 0x00000000, > + 0x0020102a, 0x00000000, 0x00000000, 0x05000036, 0x00102082, 0x00000000, 0x00004001, 0x3f800000, > + 0x06000036, 0x001020f2, 0x00000001, 0x00201e46, 0x00000000, 0x00000001, 0x01000013, 0x05000036, > + 0x00102012, 0x00000000, 0x0010000a, 0x00000000, 0x05000036, 0x00102022, 0x00000000, 0x0010001a, > + 0x00000000, 0x06000036, 0x00102042, 0x00000000, 0x0020102a, 0x00000000, 0x00000000, 0x05000036, > + 0x00102082, 0x00000000, 0x00004001, 0x3f800000, 0x06000036, 0x001020f2, 0x00000001, 0x00201e46, > + 0x00000000, 0x00000001, 0x01000013, 0x05000036, 0x00102032, 0x00000000, 0x00100086, 0x00000000, > + 0x06000036, 0x00102042, 0x00000000, 0x0020102a, 0x00000000, 0x00000000, 0x05000036, 0x00102082, > + 0x00000000, 0x00004001, 0x3f800000, 0x06000036, 0x001020f2, 0x00000001, 0x00201e46, 0x00000000, > + 0x00000001, 0x01000013, 0x0100003e, 0x54415453, 0x00000074, 0x00000019, 0x00000001, 0x00000000, > + 0x00000004, 0x00000002, 0x00000000, 0x00000000, 0x00000001, 0x00000000, 0x00000000, 0x00000000, > + 0x00000000, 0x00000000, 0x00000004, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, > + 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000001, 0x00000005, 0x00000004, 0x00000000, > + 0x00000000, 0x00000000, > + }; That looks like it still contains debug info.

May 22, 2016

Re: [PATCH v3 01/12] wined3d: Alpha test emulation for core profile contexts.

by Henri Verbeet

On 20 May 2016 at 19:55, Matteo Bruni <mbruni(a)codeweavers.com> wrote: > +static void shader_glsl_generate_alpha_test(struct wined3d_string_buffer *buffer, > + const struct wined3d_gl_info *gl_info, enum wined3d_cmp_func alpha_func) > +{ > + /* alpha_func is the PASS condition, not the DISCARD condition. Instead of > + * flipping all the operators here, just negate the comparison below. */ > + static const char * const comparison_operator[] = > + { > + "", /* WINED3D_CMP_NEVER */ > + "<", /* WINED3D_CMP_LESS */ > + "==", /* WINED3D_CMP_EQUAL */ > + "<=", /* WINED3D_CMP_LESSEQUAL */ > + ">", /* WINED3D_CMP_GREATER */ > + "!=", /* WINED3D_CMP_NOTEQUAL */ > + ">=", /* WINED3D_CMP_GREATEREQUAL */ > + "" /* WINED3D_CMP_ALWAYS */ > + }; > + > + if (alpha_func == WINED3D_CMP_ALWAYS) > + return; > + > + if (alpha_func != WINED3D_CMP_NEVER) > + shader_addline(buffer, "if (!(%s[0].a %s alpha_test_ref))\n", > + get_fragment_output(gl_info), comparison_operator[alpha_func - WINED3D_CMP_NEVER]); > + shader_addline(buffer, " discard;\n"); > +} I'm calling this good enough for a start. In case of WINED3D_CMP_EQUAL and WINED3D_CMP_NOTEQUAL in particular there may come a point where we'll have to do a range check like for color keys though.

May 22, 2016

Re: [PATCH] d3d11: Honor render state FrontCounterClockwise.

by Józef Kucia

On Sun, May 22, 2016 at 1:32 PM, Johannes Brandstätter <jbrandst(a)2ds.eu> wrote: > This fixes geometry flickering in Unigine's Valley and Heaven bechmarks. > The user interface would at least show some parts, but using this patch > it completly vanishes as well as the credits image upon closing. > > Signed-off-by: Johannes Brandstätter <jbrandst(a)2ds.eu> > --- > dlls/d3d11/device.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/dlls/d3d11/device.c b/dlls/d3d11/device.c > index 7fb28ac..d54f81f 100644 > --- a/dlls/d3d11/device.c > +++ b/dlls/d3d11/device.c > @@ -808,10 +808,11 @@ static void STDMETHODCALLTYPE d3d11_immediate_context_RSSetState(ID3D11DeviceCon > > desc = &device->rasterizer_state->desc; > wined3d_device_set_render_state(device->wined3d_device, WINED3D_RS_FILLMODE, desc->FillMode); > - wined3d_device_set_render_state(device->wined3d_device, WINED3D_RS_CULLMODE, desc->CullMode); > /* glFrontFace() */ > if (desc->FrontCounterClockwise) > - FIXME("Ignoring FrontCounterClockwise %#x.\n", desc->FrontCounterClockwise); > + wined3d_device_set_render_state(device->wined3d_device, WINED3D_RS_CULLMODE, WINED3D_CULL_CCW); > + else > + wined3d_device_set_render_state(device->wined3d_device, WINED3D_RS_CULLMODE, desc->CullMode); > /* OpenGL style depth bias. */ > if (desc->DepthBias || desc->SlopeScaledDepthBias) > FIXME("Ignoring depth bias.\n"); > -- > 2.8.1 > > > This patch doesn't make sense. The FrontCounterClockwise field needs to be mapped to glFrontFace(). The best what you can get using the current wined3d API is to invert the cull mode when FrontCounterClockwise is true. if (desc->FrontCounterClockwise) { switch (desc->CullMode) { default: case D3D11_CULL_NONE: cullmode = WINED3D_CULL_NONE; break; case D3D11_CULL_FRONT: cullmode = WINED3D_CULL_CCW; break; case D3D11_CULL_BACK: cullmode = WINED3D_CULL_CW; break; } This still is not a proper solution because the front face property can be read in shaders, see the SV_IsFrontFace system-value semantic. The proper solution is to introduce a rasterizer state object in wined3d API. You could probably start with a rasterizer state object containing a single property for FrontCounterClockwise.

May 22, 2016

Re: [PATCH] wined3d: Don't accept WINED3DFMT_NULL

by Józef Kucia

Actually, I've written the original patch. The patch won't be necessary if we ensure that a GL texture is never allocated for the WINED3DFMT_NULL format. On Sat, May 21, 2016 at 4:17 PM, Stefan Dösinger <stefandoesinger(a)gmail.com> wrote: > My sense is that a D3DFMT_NULL texture should hever have a GL texture allocated, so going through the final else path should be ok - surface_get_texture_name returns 0, and context_attach_surface_fbo ignores the other fields if object is 0. Can you check if object is != 0 in the case where it fails, and see where the value comes from? I can imagine that the game manually calls PreLoad on a NULL texture as a possible cause. In our draw and clear code we're skipping the GL texture allocation for NULL resources. Yes, the handling of WINED3DFMT_NULL textures could be improved. We should ensure that WINED3DFMT_NULL won't ever have a GL texture allocated. In the case of CS:GO, it seems that a GL texture is allocated when a draw call is issued with the D3DFMT_NULL texture attached to the texture stage 0. If I recall correctly, this happens when the loading screen is shown. The game for some reasons iterates over a set of textures, attaches each of them to the texture stage 0 and issues a draw call with a single triangle. > If the GL texture is not 0 I expect that you get a GL error before context_set_fbo_key_for_surface is run. If it is indeed 0 and something goes wrong at a later point then my reasoning above must be wrong in some way. That's accurate. The first GL error occurs when Wine tries to allocate the texture storage by calling glTexImage2D(). The error is reported because the internal format is 0 for WINED3DFMT_NULL.

May 22, 2016

Re: [PATCH] wined3d: Don't accept WINED3DFMT_NULL

by Max Qian

On 2016-05-21 9:17 am, Stefan Dösinger wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > > Hi, > > Thanks for catching this bug. You'll have to submit your patch with > your real name, and as Aaryaman stated, a signed off line. > > Am 2016-05-21 um 10:46 schrieb contrib(a)maxqia.com: >> - if (!surface) >> + if (!surface || surface->container->resource.format->id == >> WINED3DFMT_NULL) >> { >> key->objects[idx].object = 0; >> key->objects[idx].target = 0; > My sense is that a D3DFMT_NULL texture should hever have a GL texture > allocated, so going through the final else path should be ok - > surface_get_texture_name returns 0, and context_attach_surface_fbo > ignores the other fields if object is 0. Can you check if object is != > 0 in the case where it fails, and see where the value comes from? I > can imagine that the game manually calls PreLoad on a NULL texture as > a possible cause. In our draw and clear code we're skipping the GL > texture allocation for NULL resources. > > If the GL texture is not 0 I expect that you get a GL error before > context_set_fbo_key_for_surface is run. If it is indeed 0 and > something goes wrong at a later point then my reasoning above must be > wrong in some way. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJXQG4IAAoJEN0/YqbEcdMwQOQP/20p3/P+Ej25ABqMh83F9l1/ > OlhCUM3BdjYxYaZacopDInmudVALgTLaQe28dlKMw181XSqQ1op9acwHXSvXkNKM > ZyvNIsqtLxenX37ZWu0I22xqV+DFU07D4TbzrQMAlgMd9XUK2713PhNVKRuYSLpS > LazcTMldRoiHOxrJF7spbAr0Nn2JPGwHV/4NA0baQdIycnVQqztFQHPmdRVSP/eO > 9zOacv0AKDaPt3GXgJV0+S7QuDW9EEsXI6nkytDJpazBnfSrJRCVQIGhPiokf9ik > dlFkwYKuZe/fSTgSfyxyB0IhQoaOsfM4LTSJymQpneADRLhbmPORORMdzFMW/GrN > qKPgK28U2oES3u3YF6u5/2YgfrSUvJvvqPe8077Tyl60uG5W7lBWeMQ4HUDaDHgW > vWcDbvX1vYh+BG5zIvvVzGvmRKoKYnnEj65iqGqpi/vcJMz2f4ff/vmAiT1y23Hl > 0Y50ZUxTWXpUVi4uzoQlKgpmXbny2je0P2K12zbA13J3kJ/LxoHqefm1RW9VJ1w4 > VxYD94lbk4zchO0AQwbLK83b7f8QoTZH2quqyzbgyFoAynXv0RDhQ2ZjtRN66Jh+ > HmFOprGcCEmOnFs9c0JS8c9MSBVc8g1i6XmnnnccO3wyaw7vrNQbNmnqPRhkpPEV > ELMYspnFGK8apZ7633Dq > =QeKV > -----END PGP SIGNATURE----- It seems like surface_get_texture_name isn't returning 0. Code Added : diff --git a/dlls/wined3d/context.c b/dlls/wined3d/context.c index e741969..27f1d04 100644 --- a/dlls/wined3d/context.c +++ b/dlls/wined3d/context.c @@ -424,6 +424,12 @@ static inline void context_set_fbo_key_for_surface(const struct wined3d_context break; } } + if (key->objects[idx].object != 0 && surface->container->resource.format->id == WINED3DFMT_NULL) + ERR("WINED3DFMT_NULL object is %i at %x\n", key->objects[idx].object, location); + if (key->objects[idx].target != 0 && surface->container->resource.format->id == WINED3DFMT_NULL) + ERR("WINED3DFMT_NULL target is %i at %x\n", key->objects[idx].target, location); + if (key->objects[idx].level != 0 && surface->container->resource.format->id == WINED3DFMT_NULL) + ERR("WINED3DFMT_NULL level is %i at %x\n", key->objects[idx].level, location); } static void context_generate_fbo_key(const struct wined3d_context *context, Snippet from Console : (10 is WINED3D_LOCATION_TEXTURE_RGB) err:d3d:context_set_fbo_key_for_surface WINED3DFMT_NULL object is 105 at 10 err:d3d:context_set_fbo_key_for_surface WINED3DFMT_NULL target is 3553 at 10 err:d3d:context_set_fbo_key_for_surface WINED3DFMT_NULL object is 105 at 10 err:d3d:context_set_fbo_key_for_surface WINED3DFMT_NULL target is 3553 at 10 fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT (0x8cd6) fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture 104, 2048x2048, format 0x81a6. fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d texture 105, 0x0, format 0x1. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE. err:d3d:wined3d_debug_callback 0x1dd038: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.". err:d3d:device_clear_render_targets >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glClear @ ../../../source/dlls/wined3d/device.c / 509

May 22, 2016

Re: [PATCH] wined3d: Don't accept WINED3DFMT_NULL

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Thanks for catching this bug. You'll have to submit your patch with your real name, and as Aaryaman stated, a signed off line. Am 2016-05-21 um 10:46 schrieb contrib(a)maxqia.com: > - if (!surface) > + if (!surface || surface->container->resource.format->id == WINED3DFMT_NULL) > { > key->objects[idx].object = 0; > key->objects[idx].target = 0; My sense is that a D3DFMT_NULL texture should hever have a GL texture allocated, so going through the final else path should be ok - surface_get_texture_name returns 0, and context_attach_surface_fbo ignores the other fields if object is 0. Can you check if object is != 0 in the case where it fails, and see where the value comes from? I can imagine that the game manually calls PreLoad on a NULL texture as a possible cause. In our draw and clear code we're skipping the GL texture allocation for NULL resources. If the GL texture is not 0 I expect that you get a GL error before context_set_fbo_key_for_surface is run. If it is indeed 0 and something goes wrong at a later point then my reasoning above must be wrong in some way. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXQG4IAAoJEN0/YqbEcdMwQOQP/20p3/P+Ej25ABqMh83F9l1/ OlhCUM3BdjYxYaZacopDInmudVALgTLaQe28dlKMw181XSqQ1op9acwHXSvXkNKM ZyvNIsqtLxenX37ZWu0I22xqV+DFU07D4TbzrQMAlgMd9XUK2713PhNVKRuYSLpS LazcTMldRoiHOxrJF7spbAr0Nn2JPGwHV/4NA0baQdIycnVQqztFQHPmdRVSP/eO 9zOacv0AKDaPt3GXgJV0+S7QuDW9EEsXI6nkytDJpazBnfSrJRCVQIGhPiokf9ik dlFkwYKuZe/fSTgSfyxyB0IhQoaOsfM4LTSJymQpneADRLhbmPORORMdzFMW/GrN qKPgK28U2oES3u3YF6u5/2YgfrSUvJvvqPe8077Tyl60uG5W7lBWeMQ4HUDaDHgW vWcDbvX1vYh+BG5zIvvVzGvmRKoKYnnEj65iqGqpi/vcJMz2f4ff/vmAiT1y23Hl 0Y50ZUxTWXpUVi4uzoQlKgpmXbny2je0P2K12zbA13J3kJ/LxoHqefm1RW9VJ1w4 VxYD94lbk4zchO0AQwbLK83b7f8QoTZH2quqyzbgyFoAynXv0RDhQ2ZjtRN66Jh+ HmFOprGcCEmOnFs9c0JS8c9MSBVc8g1i6XmnnnccO3wyaw7vrNQbNmnqPRhkpPEV ELMYspnFGK8apZ7633Dq =QeKV -----END PGP SIGNATURE-----

May 21, 2016

Re: [PATCH resend] wined3d: Don't accept WINED3DFMT_NULL

by Aaryaman Vasishta

Hi, Thanks for the contribution! I noticed that you're missing something: On Sat, May 21, 2016 at 4:14 PM, Maxqia <contrib(a)maxqia.com> wrote: > This fixes https://bugs.winehq.org/show_bug.cgi?id=40624 > --- > dlls/wined3d/context.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > You need to sign-off on this patch. FWIW, Use git commit --amend -s to add a signed-off by field to your patch and resend it. Cheers, Aaryaman

May 21, 2016

Re: [PATCH] jscript: Date.parse: make "UTC"/"GMT" optional before the timezone offset

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=23146 Your paranoid android. === wxppro (32 bit) === Found no trace of the test summary line or of a crash === w2003std (32 bit) === Found no trace of the test summary line or of a crash === wvistau64 (32 bit) === Found no trace of the test summary line or of a crash === w2008s64 (32 bit) === Found no trace of the test summary line or of a crash === w7u (32 bit) === Found no trace of the test summary line or of a crash === w7pro64 (32 bit) === Found no trace of the test summary line or of a crash === w8 (32 bit) === Found no trace of the test summary line or of a crash === w864 (32 bit) === Found no trace of the test summary line or of a crash === w1064 (32 bit) === Found no trace of the test summary line or of a crash === wvistau64 (64 bit) === Found no trace of the test summary line or of a crash === w2008s64 (64 bit) === Found no trace of the test summary line or of a crash === w7pro64 (64 bit) === Found no trace of the test summary line or of a crash === w864 (64 bit) === Found no trace of the test summary line or of a crash === w1064 (64 bit) === Found no trace of the test summary line or of a crash

May 21, 2016