From 0ffb16bce3f61fcc1725677eb6561ab887a36637 Mon Sep 17 00:00:00 2001 From: Sorawee Porncharoenwase Date: Mon, 1 Jul 2019 21:52:31 -0700 Subject: [PATCH] Fix various typos --- racket/src/cify/README.txt | 6 +++--- racket/src/cs/README.txt | 24 ++++++++++++------------ racket/src/racket/gc/doc/README.changes | 4 ++-- racket/src/racket/gc2/gc2.h | 2 +- 4 files changed, 18 insertions(+), 18 deletions(-) diff --git a/racket/src/cify/README.txt b/racket/src/cify/README.txt index 137c7acfda..4dd77d5ca0 100644 --- a/racket/src/cify/README.txt +++ b/racket/src/cify/README.txt @@ -2,7 +2,7 @@ The "cify" compiler takes a linklet with no imports as produced by "schemify" and compiles it to C code suitable for including as part of the Racket virtual machine's implementation. -The schmeify compiler is lightly customized by a `for-cify?` flag to +The schemify compiler is lightly customized by a `for-cify?` flag to make it produce output friendlier for cify. In cify mode, schemify avoids obscuring structure-type creation, and it lifts all constants to the top. @@ -20,8 +20,8 @@ Compilation by cify is UNSAFE. For example: within the linklet with the right number of arguments. The cify pass relies on the schemify pass lift functions to avoid -closure allocation whenevr possible. The schemify pass also performs -some basic inlining, constant propoagation, and compy propagation --- +closure allocation whenever possible. The schemify pass also performs +some basic inlining, constant propagation, and copy propagation --- but it's designed to defer significantly to the back end to perform more of that. So, cify includes some copy propagation support, especially for bindings that are outside of any `lambda` form. diff --git a/racket/src/cs/README.txt b/racket/src/cs/README.txt index 28fca8232a..d6716002f3 100644 --- a/racket/src/cs/README.txt +++ b/racket/src/cs/README.txt @@ -68,8 +68,8 @@ with make PKGS="compiler-lib" -in the clone's root directory. Alternatively, use use `make -RACKET=...` to set the command for `racket`. +in the clone's root directory. Alternatively, use `make RACKET=...` +to set the command for `racket`. The use of development mode is described in more detail further below. @@ -113,7 +113,7 @@ build directory to use for building Racket-on-Chez: The resulting Racket-on-Chez executable has the suffix "cs". To generate an executable without the "cs" suffix, supply -`--enable-csdefault` to `configure`. The precense or absence of "cs" +`--enable-csdefault` to `configure`. The presence or absence of "cs" affects the location of ".zo" files. Compilation on Windows does not use the `configure` script in "c". @@ -135,7 +135,7 @@ Racket-on-Chez currently supports two compilation modes: linklets) or functions within linklets (with a "bytecode" interpreter around the compiled parts). - Select this mode by seting the `PLT_CS_MACH` environment variable, + Select this mode by setting the `PLT_CS_MACH` environment variable, but it's currently the default. In development mode or when the "cs" suffix is used for build mode, @@ -150,7 +150,7 @@ Racket-on-Chez currently supports two compilation modes: * JIT mode --- The compiled form of a module is an S-expression where individual `lambda`s are compiled on demand. - Select this mode by seting the `PLT_CS_JIT` environment variable. + Select this mode by setting the `PLT_CS_JIT` environment variable. In development mode or when the "cs" suffix is used for build mode, compiled ".zo" files in this mode are written to a "cs" @@ -281,7 +281,7 @@ Files in this directory: works. For example "demo/regexp.ss" runs the regexp matcher on a few examples. To run "demo/*.ss", use `make *-demo`. - other *.rkt - Racket scripts like "convert.rkt" or comparisions like + other *.rkt - Racket scripts like "convert.rkt" or comparisons like "demo/regexp.rkt". For example, you can run "demo/regexp.rkt" and compare the reported timing to "demo/regexp.ss". @@ -291,7 +291,7 @@ From Primitives to Modules The "expander" layer, as turned into a Chez Scheme library by "expander.sls", synthesizes primitive Racket modules such as `'#%kernel` and `'#%network`. The content of those primitive _modules_ -at the expander layer is based on primitve _instances_ (which are just +at the expander layer is based on primitive _instances_ (which are just hash tables) as populated by tables in the "primitive" directory. For example, "primitive/network.scm" defines the content of the `'#network` primitive instance, which is turned into the primitive @@ -324,12 +324,12 @@ pre-conversion form. Set `PLT_LINKLET_SHOW_JIT_DEMAND` to see forms as they are compiled on demand. In machine-code mode, set `PLT_LINKLET_SHOW_LAMBDA` to see individual -compiled terms when a linklet is not compliled whole; set -`PLT_LINKLET_SHOW_POST_LAMBDA` to see the linlet reorganized around +compiled terms when a linklet is not compiled whole; set +`PLT_LINKLET_SHOW_POST_LAMBDA` to see the linklet reorganized around those compiled parts; and/or set `PLT_LINKLET_SHOW_POST_INTERP` to see the "bytecode" form. -Set `PLT_LINKLET_SHOW_CP0` to see the Schmeified form of a linklet +Set `PLT_LINKLET_SHOW_CP0` to see the Schemified form of a linklet after expansion and optimization by Chez Scheme's cp0. Safety and Debugging Mode @@ -434,7 +434,7 @@ atomic regions: - The Racket "thread" layer provides `start-atomic` and `end-atomic` to prevent Racket-thread swaps. - These are the same opertations as provided by + These are the same operations as provided by `ffi/unsafe/atomic`. - Disabling Chez Scheme interrupts will also disable Racket @@ -447,7 +447,7 @@ atomic regions: disabling interrupts will prevent GC interrupts. The Racket "thread" layer provides `start-atomic/no-interrupts` - and `end-atomic/no-interrupts` for both declaing atomicity at + and `end-atomic/no-interrupts` for both declaring atomicity at the Racket level and turning off Chez Scheme interrupts. The combination is useful for implementing functionality that might be called in response to a GC and might also be called by diff --git a/racket/src/racket/gc/doc/README.changes b/racket/src/racket/gc/doc/README.changes index 2e622b13b2..d2eaf01014 100644 --- a/racket/src/racket/gc/doc/README.changes +++ b/racket/src/racket/gc/doc/README.changes @@ -1332,7 +1332,7 @@ Since 6.0alpha7: whether this scenario ever actually occurred. I found it while tracking down the following:) - Incremental collection did not cooperate correctly with the PARALLEL_MARK - implementation of GC_malloc_many or the local_malloc primitves. It still + implementation of GC_malloc_many or the local_malloc primitives. It still doesn't work well, but it shouldn't lose memory anymore. - Integrated some changes from the gcc source tree that I had previously missed. (Thanks to Bryce McKinley for the reminder/diff.) @@ -1774,7 +1774,7 @@ Since 6.2alpha3: - Separate gc_conf_macros.h from gc.h. - Added generic GC_THREADS client-defined macro to set the appropriate GC_XXX_THREADS internal macro. (gc_config_macros.h.) - - Add debugging versions of _ignore_off_page allocation primitves. + - Add debugging versions of _ignore_off_page allocation primitives. - Moved declarations of GC_make_closure and GC_debug_invoke_finalizer from gc.h to gc_priv.h. - Reset GC_fail_count even if only a small allocation succeeds. diff --git a/racket/src/racket/gc2/gc2.h b/racket/src/racket/gc2/gc2.h index d61b86f4d6..a901706bb9 100644 --- a/racket/src/racket/gc2/gc2.h +++ b/racket/src/racket/gc2/gc2.h @@ -261,7 +261,7 @@ GC2_EXTERN void *GC_malloc_weak_array(size_t size_in_bytes, void *replace_val); /* Alloc an array of weak pointers, initially zeroed. When a value in the array is collected, it's replaced by `replace-val'. The - precense of a pointer in the array doesn't keep the referenced + presence of a pointer in the array doesn't keep the referenced memory from being collected. See also README for information about the structure of the array. */