Piotr Caban (@piotr) commented about dlls/msvcm80/msvcm80.spec:
@ stub -arch=win64 ?_BADOFF_func@std@@YAAEB_JXZ @ stub -arch=win32 ?_Cerr_func@std@@YAAAV?$basic_ostream@DU?$char_traits@D@std@@@1@XZ @ stub -arch=win64 ?_Cerr_func@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@1@XZ -@ stub -arch=win32 ?_Cin_func@std@@YAAAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ -@ stub -arch=win64 ?_Cin_func@std@@YAAEAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ +@ cdecl -arch=win32 ?_Cin_func@std@@YAAAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ() msvcp90.?_Cin_func@std@@YAAAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ +@ cdecl -arch=win64 ?_Cin_func@std@@YAAEAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ() msvcp90.?_Cin_func@std@@YAAEAV?$basic_istream@DU?$char_traits@D@std@@@1@XZ
I'm not familiar with msvcm* dlls. I don't know if it's correct. Is the dll exporting any unmanaged functions? If so please add some tests.
It's probably best to get the changes to msvcp* dlls first and then try to figure out what can be done with msvcm.