March 2014 - Wine-Devel - list.winehq.org

Re: schedsvc: Add Task Scheduler service. Try 2.

by Alexandre Julliard

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Hi, > > Is there a reason why this patch is marked as 'pending'? It needs a more convincing argument. For instance, why do you need this service, where does the interface definition come from, why does it need a global header, why does the service need to run constantly, etc. -- Alexandre Julliard julliard(a)winehq.org

March 6, 2014

Re: GSoC 2014: Mentor signups are open

by Yaron Shahrabani

The Wine logo is not loading, do you know why? Yaron Shahrabani <Hebrew translator> On Thu, Mar 6, 2014 at 1:38 AM, Austin English <austinenglish(a)gmail.com>wrote: > Howdy, > > Signups for mentors is open. Please register at: > https://www.google-melange.com/gsoc/org2/google/gsoc2014/wine > > Our ideas page is at http://wiki.winehq.org/SummerOfCode, if you have any > ideas for projects. > > -- > -Austin > > > >

March 6, 2014

Re: [3/3] ws2_32/tests: Get rid of the do_oob_send helper function

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://newtestbot.winehq.org/JobDetails.pl?Key=5420 Your paranoid android. === wvistau64 (64 bit sock) === sock: unhandled exception c0000005 at 000007FEFF0720C0 === w2008s64 (64 bit sock) === sock: unhandled exception c0000005 at 000007FEFE4220C0

March 6, 2014

Re: [2/3] ws2_32/tests: Test OOB data more sequential by sending bidirectional

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://newtestbot.winehq.org/JobDetails.pl?Key=5419 Your paranoid android. === wvistau64 (64 bit sock) === sock: unhandled exception c0000005 at 000007FEFF0720C0

March 6, 2014

Re: [1/3] ws2_32/tests: Call WSACleanup only once

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://newtestbot.winehq.org/JobDetails.pl?Key=5418 Your paranoid android. === w2000pro (32 bit sock) === sock.c:613: Test failed: oob_server (464): unexpectedly at the OOB mark: 0 === wxppro (32 bit sock) === sock.c:613: Test failed: oob_server (b24): unexpectedly at the OOB mark: 0 === wvistau64 (32 bit sock) === sock.c:613: Test failed: oob_server (744): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:613: Test failed: oob_server (768): unexpectedly at the OOB mark: 0 === wvistau64 (64 bit sock) === sock.c:613: Test failed: oob_server (744): unexpectedly at the OOB mark: 0 === w2008s64 (64 bit sock) === sock.c:613: Test failed: oob_server (654): unexpectedly at the OOB mark: 0

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Dmitry Timoshkov

Hi, Is there a reason why this patch is marked as 'pending'? -- Dmitry.

March 6, 2014

GSoC 2014: Mentor signups are open

by Austin English

Howdy, Signups for mentors is open. Please register at: https://www.google-melange.com/gsoc/org2/google/gsoc2014/wine Our ideas page is at http://wiki.winehq.org/SummerOfCode, if you have any ideas for projects. -- -Austin

March 5, 2014

Re: kernel32: Cache locale info from the registry.

by Alexandre Julliard

Vincent Povirk <madewokherd(a)gmail.com> writes: > + case LOCALE_ICALENDARTYPE: *cache_index = 0; return iCalendarTypeW; > + case LOCALE_ICURRDIGITS: *cache_index = 1; return iCurrDigitsW; > + case LOCALE_ICURRENCY: *cache_index = 2; return iCurrencyW; > + case LOCALE_IDIGITS: *cache_index = 3; return iDigitsW; > + case LOCALE_IFIRSTDAYOFWEEK: *cache_index = 4; return iFirstDayOfWeekW; > + case LOCALE_IFIRSTWEEKOFYEAR: *cache_index = 5; return iFirstWeekOfYearW; > + case LOCALE_ILZERO: *cache_index = 6; return iLZeroW; > + case LOCALE_IMEASURE: *cache_index = 7; return iMeasureW; > + case LOCALE_INEGCURR: *cache_index = 8; return iNegCurrW; > + case LOCALE_INEGNUMBER: *cache_index = 9; return iNegNumberW; > + case LOCALE_IPAPERSIZE: *cache_index = 10; return iPaperSizeW; > + case LOCALE_ITIME: *cache_index = 11; return iTimeW; > + case LOCALE_S1159: *cache_index = 12; return s1159W; > + case LOCALE_S2359: *cache_index = 13; return s2359W; > + case LOCALE_SCURRENCY: *cache_index = 14; return sCurrencyW; > + case LOCALE_SDATE: *cache_index = 15; return sDateW; > + case LOCALE_SDECIMAL: *cache_index = 16; return sDecimalW; > + case LOCALE_SGROUPING: *cache_index = 17; return sGroupingW; > + case LOCALE_SLIST: *cache_index = 18; return sListW; > + case LOCALE_SLONGDATE: *cache_index = 19; return sLongDateW; > + case LOCALE_SMONDECIMALSEP: *cache_index = 20; return sMonDecimalSepW; > + case LOCALE_SMONGROUPING: *cache_index = 21; return sMonGroupingW; > + case LOCALE_SMONTHOUSANDSEP: *cache_index = 22; return sMonThousandSepW; > + case LOCALE_SNEGATIVESIGN: *cache_index = 23; return sNegativeSignW; > + case LOCALE_SPOSITIVESIGN: *cache_index = 24; return sPositiveSignW; > + case LOCALE_SSHORTDATE: *cache_index = 25; return sShortDateW; > + case LOCALE_STHOUSAND: *cache_index = 26; return sThousandW; > + case LOCALE_STIME: *cache_index = 27; return sTimeW; > + case LOCALE_STIMEFORMAT: *cache_index = 28; return sTimeFormatW; > + case LOCALE_SYEARMONTH: *cache_index = 29; return sYearMonthW; You clearly want some sort of array here. -- Alexandre Julliard julliard(a)winehq.org

March 5, 2014

Re: [PATCH 2/5] d3dx9: Always use type->Rows as D3DXPC_MATRIX_ROWS parameters size. (resend)

by Matteo Bruni

2014-03-05 17:37 GMT+01:00 Rico Schüller <kgbricola(a)web.de>: > On 03.03.2014 17:48, Matteo Bruni wrote: >> >> diff --git a/dlls/d3dx9_36/tests/shader.c b/dlls/d3dx9_36/tests/shader.c >> index 74ada6e..80c0f64 100644 >> --- a/dlls/d3dx9_36/tests/shader.c >> +++ b/dlls/d3dx9_36/tests/shader.c >> @@ -120,7 +120,7 @@ static const DWORD ctab_matrices[] = { >> 0x000000ac, >> 0x00000058, 0x00070002, 0x00000001, 0x00000064, 0x00000000, >> /* Constant 1 desc (fmatrix3x1) */ >> 0x00000074, 0x00000002, 0x00000004, 0x00000080, 0x00000000, >> /* Constant 2 desc (fmatrix4x4) */ >> - 0x00000090, 0x00040002, 0x00000003, 0x0000009c, 0x00000000, >> /* Constant 3 desc (imatrix2x3) */ >> + 0x00000090, 0x00040002, 0x00000002, 0x0000009c, 0x00000000, >> /* Constant 3 desc (imatrix2x3) */ > > Why this? Was the shader blob wrong (invalid)? Or did you just compile with > vs without optimization? > AFAICT that shader bytecode was hand-generated and specifically that constant was wrongly given 3 registers instead of 2. We still differ from native in that, in cases like this where a constant is assigned more registers than it would naturally need, we only allocate the minimum required, while native sometimes just uses the register size stored in the shader (which is the reason this test passed on native). Since that kind of overallocation doesn't seem to happen in real shaders generated by D3DCompile() / fxc.exe I don't think that is an issue we should care of.

March 5, 2014

Re: [PATCH 2/5] d3dx9: Always use type->Rows as D3DXPC_MATRIX_ROWS parameters size. (resend)

by Rico Schüller

On 03.03.2014 17:48, Matteo Bruni wrote: > diff --git a/dlls/d3dx9_36/tests/shader.c b/dlls/d3dx9_36/tests/shader.c > index 74ada6e..80c0f64 100644 > --- a/dlls/d3dx9_36/tests/shader.c > +++ b/dlls/d3dx9_36/tests/shader.c > @@ -120,7 +120,7 @@ static const DWORD ctab_matrices[] = { > 0x000000ac, > 0x00000058, 0x00070002, 0x00000001, 0x00000064, 0x00000000, /* Constant 1 desc (fmatrix3x1) */ > 0x00000074, 0x00000002, 0x00000004, 0x00000080, 0x00000000, /* Constant 2 desc (fmatrix4x4) */ > - 0x00000090, 0x00040002, 0x00000003, 0x0000009c, 0x00000000, /* Constant 3 desc (imatrix2x3) */ > + 0x00000090, 0x00040002, 0x00000002, 0x0000009c, 0x00000000, /* Constant 3 desc (imatrix2x3) */ Why this? Was the shader blob wrong (invalid)? Or did you just compile with vs without optimization? > 0x74616D66, 0x33786972, 0xab003178, /* Constant 1 name */ > 0x00030003, 0x00010003, 0x00000001, 0x00000000, /* Constant 1 type desc */ > 0x74616D66, 0x34786972, 0xab003478, /* Constant 2 name */ > @@ -133,8 +133,9 @@ static const DWORD ctab_matrices[] = { > > static const D3DXCONSTANT_DESC ctab_matrices_expected[] = { > {"fmatrix4x4", D3DXRS_FLOAT4, 0, 4, D3DXPC_MATRIX_COLUMNS, D3DXPT_FLOAT, 4, 4, 1, 0, 64, NULL}, > - {"imatrix2x3", D3DXRS_FLOAT4, 4, 3, D3DXPC_MATRIX_ROWS, D3DXPT_INT, 2, 3, 1, 0, 24, NULL}, > - {"fmatrix3x1", D3DXRS_FLOAT4, 7, 1, D3DXPC_MATRIX_COLUMNS, D3DXPT_FLOAT, 3, 1, 1, 0, 12, NULL}}; > + {"imatrix2x3", D3DXRS_FLOAT4, 4, 2, D3DXPC_MATRIX_ROWS, D3DXPT_INT, 2, 3, 1, 0, 24, NULL}, > + {"fmatrix3x1", D3DXRS_FLOAT4, 7, 1, D3DXPC_MATRIX_COLUMNS, D3DXPT_FLOAT, 3, 1, 1, 0, 12, NULL}, > +}; > > static const DWORD ctab_matrices2[] = { > 0xfffe0200, /* vs_2_0 */ >

March 5, 2014