On Tue, 16 Sep 2008, Szak�ts Viktor wrote: Hi Viktor,
>> 2. we can change used ABI so each Harbour function which may >> need HVM access will receive pointer to HB_STACK. Quite easy >> for HB_FUNC() but for internal ones it will force much more >> jobs. > One vote for this one. > Wouldn't this increase the size of -gc3 compiled apps, due > to passing a pointer for every VM calls? Yes it will. But it will and it will have some speed overhead for single thread programs but much smaller then accessing TLS which on some platforms where there is no native TLS support is very huge. But it will also mean that we will drop binary compatibility with all existing tools. I like this idea but I do not want to start such modification as long as we will not know how current code works on different platforms and what other problems we may found which will be good to resolve together. BTW does anyone tried to use threads with DMC? I create DMC builds in my Linux box with and without HB_USE_TLS but in both cases hbtest crashes on MT test code I added. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
