>> I've just seen David's latest tests... IMO if there >> is no reasonable solution for it, removing -s could >> still be a fallback option, for the reason that >> watcom/os2 is not a primary target, I mean no one >> seems to use it for production, in practice we need it >> only for cross-platform build testing of OS/2 and >> in this case speed doesn't matter at all. >> Of course it'd nicer if it's fast, but doesn't seem >> to be a priority. > > Recent David tests shows that removing -s form OW build > flags to enable stack debug code is not enough workaround. > The problem can be still exploited by CRTL code which is > compiled without stack debug code and can executed APIENTRY16 > functions. We have such situation in GTSTD which use kbhit() > and getch() CRTL functions. > So the only effect we can reach by removing -s is very serious > speed overhead but it will not change current runtime behavior > of Harbour applications.
Okay, that clears it up. So in essence OpenWatcom for OS/2 is broken whatever we do in Harbour. [ In this case though, we may safely readd -s for all modules, thus deleting our little hack and wait for Watcom team to fix it. ] Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
