Hello
This mail is mainly for the people that made the QNX4 porting, but may be
someone may help.

I am a newbie to X. I downloaded and successfully installed XFree86 R6,
Version 4.2.0 on
QNX 4.25, using Watcom 10.6 Patch B from QSSL. I managed to run it even on
TCP/IP 4.23 ( no unix sockets ) by �telling� the server not to use UNIXCONN,
but only TCPCONN.
Also, because I don�t have crypt, nor login3s.lib ( only the 3r version ) I
changed the related option to wcc, by using -5r, and changing the -l option
to that library.

My question regards about the �giant� stack size for the Xserver: 4 Mb is a
lot ! and I am intrigued why this enormous stack. I tried to dive the
sources for an intensive use of alloca, but to no clear
result.
Could someone ( the QNX porting authors, or someone else ) tell me if I can
confidently reduce the
stack size, and in such a case, which should be a reasonable figure ?
Note, for not QNX/Watcom users: the -xr ( i.e, -5r ) tells the compiler to
generate functions calls using registers where possible, as opposed to -xs,
which directs it to only use the stack for argument passing. With all the
code generated this way, the stack usage is greatly reduced. So, the only
source for a big stack need could come from very large/deep recursive calls,
from large locals, or from alloca usage.
Thank you
Marcelo Nicolet
PS. Incidentally ... when compiling in -xr mode, Watcom reports an error
whenever a function call
does not follows the prototype ( except, of course, it�s declared as
variadic ).
This was the case in lib/X11/omGeneric.c, line 1129, when calling
parse_fontdata( ), which I easily corrected adding a dummy FontDataRec
argument.
PS2. For those potentially interested: Aside the correction mentioned above,
I made another important one ( again, Watcom stuff ) to .../BUSmemcpy.c, and
to a few Makefiles.
The changes are somewhat brute force, so I am not sure how I can contribute
them to the main
source tree.


_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to