- Aug 31, 2004
-
-
rtoy authored
the places where it is used. o Remove old bignum-gcd.
-
- Aug 30, 2004
-
-
rtoy authored
o Previous changes were wrong. This version handles relative and section-relative columns correctly, I think. PPRINT-TABULAR o The computation of colinc was wrong---I don't think we need to add one to tabsize. o I don't think we should output the space character. It results in one extra space. With these changes, the format tests in ansi-tests for ~T and friends pass. I think these are right now, but I'm not 100% sure.
-
rtoy authored
(debug-return). No bootstrap file or cross-compile needed. Return-from-frame only works when debug = 3.
-
- Aug 28, 2004
-
-
rtoy authored
tabbing.
-
rtoy authored
was at or beyond colnum. o COMPUTE-TAB-SIZE was crashing if colinc was zero, instead of returning 0. o PPRINT-TABULAR was passing the specified tabsize to PPRINT-TAB. I think it should be incremented by one to specify the correct colinc for PPRINT-TAB. These fixes correct some of the errors found by ANSI-TESTS.
-
rtoy authored
-
- Aug 27, 2004
-
-
rtoy authored
-
rtoy authored
output. (ANSI-TEST FORMAT.S.8.)
-
rtoy authored
differences in rounding for the range of numbers where PRIN1 uses the same style of output as ~F. This is due to how PRIN1 uses FLONUM-TO-DIGITS to produce the result, but ~F was using FLOAT-STRING. Hack it so FLONUM-TO-STRING calls FLONUM-TO-DIGITS when possible.
-
rtoy authored
it was checking with minusp).
-
rtoy authored
o "~,,,',A" was incorrectly parsed: The fill character is ",". o (FORMAT NIL "~VD" NIL 7) was not treating a NIL value for V to mean use the default. o "~3,,-1A" would add one pad character. I think this is allowed, but not the intent. The extra pad character(s) are no longer produced. o ~F was printing numbers in exponential notation if the number was too large or small. We know print out all the necessary digits, even though we're allowed to use exponential notation if more than 100 digits would be produced. o Correctly handle justification (~< ~>) with non-zero minpad value.
-
rtoy authored
"1234567." We just test to see if the width is large enough to hold the number. If not, increase the width so that float-string will produce enough digits.
-
- Aug 23, 2004
- Aug 22, 2004
- Aug 20, 2004
- Aug 17, 2004
- Aug 16, 2004
-
-
rtoy authored
non-negative when one arg was negative but the other was not. Should fix the segfault for the misc.306 ansi test.
-
- Aug 13, 2004
-
-
emarsden authored
to localhost. Responsibility for calling GET-BEST-AUTHORIZATION was distributed between EXT:OPEN-CLX-DISPLAY and XLIB:OPEN-DISPLAY; all authorization handling has been moved to XLIB:OPEN-DISPLAY. O-C-D now only deals with parsing $DISPLAY. This rearrangement should fix X11 authorization problems seen with servers that don't listen to TCP connection requests, and thus don't create an MIT-MAGIC-COOKIE for TCP connections.
-
emarsden authored
-
emarsden authored
Bruno Haible).
-
- Aug 12, 2004
-
-
rtoy authored
-
- Aug 09, 2004
- Aug 08, 2004
- Aug 07, 2004
-
-
pmai authored
for the cross-compiler itself with create-target.sh isn't needed, since cross-build-world.sh does this by itself already.
-
- Aug 06, 2004
- Aug 04, 2004
-
-
rtoy authored
algorithm to make the bignums roughly the same size before running binary gcd.
-
rtoy authored
foreign functions for linkage table stuff. (This should probably be changed.) In cold-fdefinition-object and cold-fset, we call lookup-foreign-symbol and stuff away the address of the entry in the linkage-table. I think we really want the contents of the entry since that contains the actual address for these functions. Thus, change lookup-foreign-symbol to take an link-type arg, and for sparc, when the link-type is :data, return the value from the linkage-table entry instead of returning the address of the linkage-table entry. I hope this fixes the occasional problem with undefined functions giving sigbus instead of an undefined-function error when loading kernel.core.
-
cwang authored
Change offset_vector back to an unsigned int* because it still has 32-bit elements on amd64. Eventually we will make this consistent with internals.h. This creates a compiler warning, sigh.
-