[PATCH] msvcr110: Create current scheduler in _CurrentScheduler::_Id

[Daniel Lehman]

> Shouldn't something similar be also done for _CurrentScheduler::_Id?

yeah, but not sure how to automate testing for it.  once either  _GetNumberOfVirtualProcessors or _Id is called, the scheduler is created and I don't know how to kill it

in the attached test, you can comment out either call to the underscore version and both the non-underscore versions (GetNumberOfVirtualProcessors and Id) still pass

[Piotr Caban]

Signed-off-by: Piotr Caban <piotr(a)codeweavers.com>

[Piotr Caban]

Hi Daniel,

On 07/19/18 00:44, Daniel Lehman wrote:
> > Shouldn't something similar be also done for _CurrentScheduler::_Id?
>
> yeah, but not sure how to automate testing for it.  once either  _GetNumberOfVirtualProcessors or _Id is called, the scheduler is created and I don't know how to kill it
>
> in the attached test, you can comment out either call to the underscore version and both the non-underscore versions (GetNumberOfVirtualProcessors and Id) still pass
> As far as I know there's no way of destroying current scheduler. You 
> can run tests in separate thread if you need the scheduler to be not 
> initialized (I don't think we need it now).

Thanks,
Piotr