diff options
| author | Ivan Maidanski <ivmai@mail.ru> | 2021-11-25 21:45:21 +0300 |
|---|---|---|
| committer | Ivan Maidanski <ivmai@mail.ru> | 2021-12-21 11:52:26 +0300 |
| commit | afb1efaac875af50761fb959b0dbdd2a95438d14 (patch) | |
| tree | 4ae7b7f62ba94ee672660f3ea78c84c81aad39c0 | |
| parent | 0d236b3212932d40f5d30cec5d320163f7919a84 (diff) | |
| download | bdwgc-afb1efaac875af50761fb959b0dbdd2a95438d14.tar.gz | |
Fix a typo in debugging.html
(a cherry-pick of commit d1a84f594 from 'release-8_0')
* doc/debugging.html (Unexpectedly Large Heap): Fix typo "primitives in",
add missing space after it.
| -rw-r--r-- | doc/debugging.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/debugging.html b/doc/debugging.html index 5c24862b..42753b70 100644 --- a/doc/debugging.html +++ b/doc/debugging.html @@ -182,7 +182,7 @@ pseudo-random numbers, and the like. It is also likely to improve GC performance, perhaps drastically so if the application is paging. <LI> If you allocate large objects containing only one or two pointers at the beginning, either try the typed allocation -primitives is <TT>gc_typed.h</tt>, or separate out the pointer-free component. +primitives in <TT>gc_typed.h</tt>, or separate out the pointer-free component. <LI> Consider using <TT>GC_malloc_ignore_off_page()</tt> to allocate large objects. (See <TT>gc.h</tt> and above for details. Large means > 100K in most environments.) |