Mail Archives: djgpp-workers/2001/01/01/17:03:21
Hello.
"Peter J. Farley III" wrote:
>
> Richard Dawe wrote:
> >I get the same results as you, but the output has file descriptor 7
> >rather than 5.
[snip]
> You ran them from inside bash. I ran under COMMAND.COM to get the *.ok
> files. When I run them under bash I get the same results as you, fd =
> 7. I think bash has more open file descriptors while running, so I
> think that explains the difference.
Yes, I used bash.
> Nope, you got them all in that version of the patches. Thanks for the
> testing and report. Please also try version #3a of the main patch,
> posted yesterday, Dec. 31.
I did apply version #3a, but I missed the inherit test. I get the same
results as you - again, under bash, with higher file descriptors in the
results.
> Under gcc 2.952 on my system (as.exe version 2.9.5 from bnu2951b.zip),
> gas complains that the ljmp/lcall operands are (are not? I forget now
> which way it went) indirect. Adding a "*" operator in front of the
> operands quiets the message. Eli advised they should be fixed, even
> though they do not stop the make, nor did it seem (in the early days of
> my testing, not tested without that patch since then) to affect the
> running of libc functions and tests.
While trying to fix similar warnings in libsocket, I found that the code
generated for lcall was the same with or without the '*'. I did not
compare code generation for ljmp. I have to say that the current solution
for DJGPP are more elegant than the one I used in libsocket, libwin.
Thanks, bye, Rich =]
--
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]
- Raw text -