Hi Przemek,
> * harbour/source/vm/fm.c > % use DLMALLOC as default memory manager in OpenWatcom Windows builds. > Warning: HB_FM_DLMT_ALLOC does not work with OpenWatcom. > Thanks. > * harbour/config/dos/owatcom.cf > * harbour/config/win/owatcom.cf > * harbour/config/linux/owatcom.cf > * harbour/config/os2/owatcom.cf > * changed alignment settings from 8 to 4 > * synced optimization flags used in different builds > ! fixed linker parameters when HB_BUILD_DEBUG=yes is set > ; TOVERIFY: I do not remember what calling convention should be used > in OpenWatcom MT OS2 builds to eliminate GPF when APIENTRY16 functions > are called. It's possible that current settings are wrong. > They almost surely *are* wrong. I've just copied them from win version in the hope OS/2 users will be interested and tweak it. > * harbour/config/win/owatcom.cf > * removed STACK=65536 from OpenWatcom linker parameters. > This switch probably was inherited from old DOS WatcomC builds. > Later I'll test current OpwnWatcom builds to check if we can also > remove it from DOS builds when cwstub.exe is used. > * restored -bm switch. When DLMALLOC is used it does not cause > noticeable performance reduction. > * use default register calling convention. We can change it > in the future but 1-st we should check the performance overhead. > If calling convention is a problem only for .DLLs then it can > be resolved by modifying HB_EXTERN declaration and adding function > attributes which will force given calling convention. > Thanks, IMO we must do this as the definitive goal is to have interchangeable harbour dll. This is very important and one of the main points of .dlls. Notice that .dll support in win/owatcom is broken due some startup procedure problems. * harbour/config/linux/owatcom.cf > * enabled pentium pro instruction in OpenWatcom Linux builds. > It reduces the code size and increase performance a little bit. > Windows users which do not need pure pentium CPU support can make > the same. > We're already PPro level for some compiler, so IMO it's safe to do for win/owatcom. > * harbour/utils/hbmk2/hbmk2.prg > ! fixed OpenWatcom calling convention settings. Viktor you cannot chose > simultaneously register and stack calling convention. You have to > chose > one and keep it synced with Harbour compile time settings. Otherwise > you will have unresolved external or you will force creating by linker > dynamically function call wrappers (of course if OW support such > functionality) what may strongly reduce the performance. > Well, I just copied them from .cf files, which weren't developed by me, so don't blame me :) After settling with the switches in .cf files I was planning to do a sync with hbmk2. It's in the included TODO list. Thanks for your changes. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
