diff options
author | Ivan Maidanski <ivmai@mail.ru> | 2021-10-18 21:09:10 +0300 |
---|---|---|
committer | Ivan Maidanski <ivmai@mail.ru> | 2021-10-18 21:09:10 +0300 |
commit | 09fdbf154480c222d0c6409873bfe1888634cf3c (patch) | |
tree | 798a38377e563ca60d23645888edbbf0b2ca40bb | |
parent | 6beefe83c068d0df4e487e68a1309fdff0176a05 (diff) | |
download | bdwgc-09fdbf154480c222d0c6409873bfe1888634cf3c.tar.gz |
Fix capital case of setjmp_test and gctest in README and comments
* Makefile.direct (HOSTCFLAGS): Start setjmp_test word with lower case
in comment.
* README.md (Installation and Portability): Likewise.
* mach_dep.c (GC_with_callee_saves_pushed): Likewise.
* tools/setjmp_t.c (main): Likewise.
* Makefile.direct (setjmp_test): Start gctest word with lower case in
comment.
* OS2_MAKEFILE (CFLAGS): Likewise.
* README.md (Installation and Portability): Likewise.
* SMakefile.amiga (finalize.o): Likewise.
-rw-r--r-- | Makefile.direct | 4 | ||||
-rw-r--r-- | OS2_MAKEFILE | 2 | ||||
-rw-r--r-- | README.md | 6 | ||||
-rw-r--r-- | SMakefile.amiga | 2 | ||||
-rw-r--r-- | mach_dep.c | 2 | ||||
-rw-r--r-- | tools/setjmp_t.c | 4 |
6 files changed, 10 insertions, 10 deletions
diff --git a/Makefile.direct b/Makefile.direct index fc4db7ef..c74660c1 100644 --- a/Makefile.direct +++ b/Makefile.direct @@ -69,7 +69,7 @@ HOSTCFLAGS=$(CFLAGS) # For dynamic library builds, it may be necessary to add flags to generate # PIC code, e.g. -fPIC on Linux. -# Setjmp_test may yield overly optimistic results when compiled +# setjmp_test may yield overly optimistic results when compiled # without optimization. # Look into doc/README.macros for the description of the "define arguments" @@ -389,7 +389,7 @@ gctest$(EXEEXT): tests/test.o base_lib $(UTILS) ./if_not_there gctest$(EXEEXT) || $(CC) $(CFLAGS) -o gctest$(EXEEXT) tests/test.o gc.a `./threadlibs` # If an optimized setjmp_test generates a segmentation fault, -# odds are your compiler is broken. Gctest may still work. +# odds are your compiler is broken. gctest may still work. # Try compiling setjmp_t.c unoptimized. setjmp_test$(EXEEXT): $(srcdir)/tools/setjmp_t.c $(srcdir)/include/gc.h \ $(UTILS) diff --git a/OS2_MAKEFILE b/OS2_MAKEFILE index a5216316..e8f67073 100644 --- a/OS2_MAKEFILE +++ b/OS2_MAKEFILE @@ -12,7 +12,7 @@ CORDOBJS= cord\cordbscs.obj cord\cordxtra.obj cord\cordprnt.obj CC= icc CFLAGS= /O /Q /DALL_INTERIOR_POINTERS /DENABLE_DISCLAIM /DGC_ATOMIC_UNCOLLECTABLE /DGC_GCJ_SUPPORT /DJAVA_FINALIZATION /DNO_EXECUTE_PERMISSION /DSMALL_CONFIG # Use /Ti instead of /O for debugging -# Setjmp_test may yield overly optimistic results when compiled +# setjmp_test may yield overly optimistic results when compiled # without optimization. all: gc.lib cord.lib @@ -203,10 +203,10 @@ atomic intrinsics. Below we focus on the collector build using classic makefile. For the Makefile.direct-based process, typing `make check` instead of `make` will automatically build the collector and then run `setjmp_test` and `gctest`. -`Setjmp_test` will give you information about configuring the collector, which is -useful primarily if you have a machine that's not already supported. Gctest is +`setjmp_test` will give you information about configuring the collector, which is +useful primarily if you have a machine that's not already supported. gctest is a somewhat superficial test of collector functionality. Failure is indicated -by a core dump or a message to the effect that the collector is broken. Gctest +by a core dump or a message to the effect that the collector is broken. gctest takes about a second to two to run on reasonable 2007 vintage desktops. It may use up to about 30 MB of memory. (The multi-threaded version will use more. 64-bit versions may use more.) `make check` will also, as its last step, diff --git a/SMakefile.amiga b/SMakefile.amiga index d481f986..64941375 100644 --- a/SMakefile.amiga +++ b/SMakefile.amiga @@ -119,7 +119,7 @@ blacklst.o : blacklst.c $(INC) finalize.o : finalize.c $(INC) $(CC) finalize.c $(SCOPT) noopt -# Could sas/c still have problems with this one? Gctest sometimes fails to finalize all. +# Could sas/c still have problems with this one? gctest sometimes fails to finalize all. new_hblk.o : new_hblk.c $(INC) $(CC) new_hblk.c $(SCOPT) @@ -312,7 +312,7 @@ GC_INNER void GC_with_callee_saves_pushed(void (*fn)(ptr_t, void *), word * i = (word *)®s; ptr_t lim = (ptr_t)(®s) + sizeof(regs); - /* Setjmp doesn't always clear all of the buffer. */ + /* setjmp doesn't always clear all of the buffer. */ /* That tends to preserve garbage. Clear it. */ for (; (word)i < (word)lim; i++) { *i = 0; diff --git a/tools/setjmp_t.c b/tools/setjmp_t.c index 254803ca..419bbb32 100644 --- a/tools/setjmp_t.c +++ b/tools/setjmp_t.c @@ -121,11 +121,11 @@ int main(void) (void)SETJMP(b); if (y == 1) { if (x == 2) { - printf("Setjmp-based generic mark_regs code probably won't work.\n"); + printf("setjmp-based generic mark_regs code probably won't work.\n"); printf("But we rarely try that anymore. If you have getcontect()\n"); printf("this probably doesn't matter.\n"); } else if (x == 1) { - printf("Setjmp-based register marking code may work.\n"); + printf("setjmp-based register marking code may work.\n"); } else { printf("Very strange setjmp implementation.\n"); } |