> > > After recent owatcom tweaks, its performance went back to a very good > level > > in ST mode. > > msvc ST: 29s MT: 49s > > mingw ST: 34s > > owatcom ST: 38s MT: 75s > > pocc ST: 44s > > bcc ST: 46s > > owatcom (yesterday) ST: 54s > > And this is without register calling, so if we manage to solve it, a > little > > can be shaved off of this result even. > > Please try it with register calling convention. > In my test the difference is really huge. > > > So this means owatcom is a good 3rd in most aspects. It still has > > some missing/broken feature though to get in on par with first level > > compilers. > > With stack calling convention above are not representative results.
Yes, but we need to take care of the .dll problem. For me, optimizing by losing important features isn't an option. I hope someone will show how to solve this optimally, until then HB_USER_CFLAGS can be used to override the defaults if someone needs maximum speed. After 64-bit builds are finished cleanly, I'll make some tests with register calling, in the hope this will stir up the interest to solve this. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
