Re: [PATCH 0/3] MR758: d3d10: Test D3D10CreateEffectFromMemory.

[Nikolay Sivov (＠nsivov)]

Nikolay Sivov (@nsivov) commented about dlls/d3d10/tests/effect.c:
> - if (strcmp(winetest_platform, "wine")) /* Crash on wine. */
> - {
> - hr = create_effect(buffer, 0, NULL, NULL, &effect);
> - ok(hr == D3DERR_INVALIDCALL, "Got unexpected hr %#lx.\n", hr);
> - ok(!memcmp(buffer, fx_test_ecbt, sizeof(fx_test_ecbt)), "Data is not modified.\n");
> - }
> -
> - hr = create_effect(buffer, 0, device, NULL, &effect);
> - ok(hr == S_OK, "Got unexpected hr %#lx.\n", hr);
> - ok(!memcmp(buffer, fx_test_ecbt, sizeof(fx_test_ecbt)), "Data is not modified.\n");
> - effect->lpVtbl->Release(effect);
> -
> - hr = create_effect(buffer, D3D10_EFFECT_COMPILE_ALLOW_SLOW_OPS, device, NULL, &effect);
> - ok(hr == S_OK, "Got unexpected hr %#lx.\n", hr);
> - ok(!memcmp(buffer, fx_test_ecbt, sizeof(fx_test_ecbt)), "Data is not modified.\n");
> - effect->lpVtbl->Release(effect);

Could you explain, where does this come from? Why would you think that input blob would ever change?