From 72dfe176f5211f561263984a2df653f16dcf5466 Mon Sep 17 00:00:00 2001
From: Jacek Sieka <arnetheduck@gmail.com>
Date: Mon, 23 Apr 2018 17:02:38 +0800
Subject: remove dead code elimination option (#7669)

---
 doc/manual.rst | 16 ----------------
 1 file changed, 16 deletions(-)

(limited to 'doc/manual.rst')

diff --git a/doc/manual.rst b/doc/manual.rst
index fbd043020..f1330d524 100644
--- a/doc/manual.rst
+++ b/doc/manual.rst
@@ -6768,22 +6768,6 @@ the created global variables within a module is not defined, but all of them
 will be initialized after any top-level variables in their originating module
 and before any variable in a module that imports it.
 
-deadCodeElim pragma
--------------------
-The ``deadCodeElim`` pragma only applies to whole modules: It tells the
-compiler to activate (or deactivate) dead code elimination for the module the
-pragma appears in.
-
-The ``--deadCodeElim:on`` command line switch has the same effect as marking
-every module with ``{.deadCodeElim:on}``. However, for some modules such as
-the GTK wrapper it makes sense to *always* turn on dead code elimination -
-no matter if it is globally active or not.
-
-Example:
-
-.. code-block:: nim
-  {.deadCodeElim: on.}
-
 
 ..
   NoForward pragma
-- 
cgit 1.4.1-2-gfad0