summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortoonn <ghc@toonn.io>2020-08-22 14:14:22 +0200
committertoonn <ghc@toonn.io>2020-08-22 14:14:22 +0200
commitf8f595152dbb9ba46896c43870e327724a2f8fdf (patch)
tree73db4d9e69735d307c8b58ab447214b1bf78b284
parent82f15edc506cdf91c63c2351603c8f0fb0379914 (diff)
downloadhaskell-f8f595152dbb9ba46896c43870e327724a2f8fdf.tar.gz
Fix typos in Runtime system section of 8.10.1 notes
-rw-r--r--docs/users_guide/8.10.1-notes.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/users_guide/8.10.1-notes.rst b/docs/users_guide/8.10.1-notes.rst
index b2fe3ef85c..9a259bd7dd 100644
--- a/docs/users_guide/8.10.1-notes.rst
+++ b/docs/users_guide/8.10.1-notes.rst
@@ -281,13 +281,13 @@ Runtime system
~~~~~~~~~~~~~~
- The runtime system linker now marks loaded code as non-writable (see
- :ghc-ticket:`14069`) on all tier-1 platforms. This is necesaary for
+ :ghc-ticket:`14069`) on all tier-1 platforms. This is necessary for
out-of-the-box compatibility with OpenBSD and macOS Catalina (see
:ghc-ticket:`17353`)
- The RTS API now exposes :ref:`an interface <event_log_output_api>` to
- configure ``EventLogWriters``, allowing eventlog data to fed to sinks other
- than ``.eventlog`` files.
+ configure ``EventLogWriters``, allowing eventlog data to be fed to sinks
+ other than ``.eventlog`` files.
- A new ``+RTS`` flag ``--disable-delayed-os-memory-return`` was added to make
for accurate resident memory usage of the program as shown in memory
@@ -298,9 +298,9 @@ Runtime system
Using this new flag is expected to make the program slightly slower.
Without this flag, the (Linux) RTS returns unused memory "lazily" to the OS.
- This has making the memory available to other processes while also allowing
- the RTS to re-use the memory very efficiently (without zeroing pages) in case
- it needs it again, but common tools will incorrectly show such memory as
+ This makes the memory available to other processes while also allowing the
+ RTS to re-use the memory very efficiently (without zeroing pages) in case it
+ needs it again, but common tools will incorrectly show such memory as
occupied by the RTS (because they do not process the ``LazyFree`` field in
``/proc/PID/smaps``).