diff --git a/docs/source/using_yosys/bugpoint.rst b/docs/source/using_yosys/bugpoint.rst
index a74693fa3..a81c36b27 100644
--- a/docs/source/using_yosys/bugpoint.rst
+++ b/docs/source/using_yosys/bugpoint.rst
@@ -99,8 +99,9 @@ How do I use bugpoint?
     design.il`` to print only the error message(s) and use that (or a portion of
     that) as the ``<string>`` to search for
 
-- ``-modules``, ``-ports``, ``-cells``, and ``-processes`` will enable those
-  parts of the design to be removed (default is to allow removing all)
+- ``-modules``, ``-ports``, ``-cells``, ``-processes``, and ``-wires`` will
+  enable only those parts of the design to be removed (default is to allow
+  removing all)
 
   + use the ``bugpoint_keep`` attribute on objects you don't want to be
     removed, usually because you already know they are related to the failure
diff --git a/passes/cmds/bugpoint.cc b/passes/cmds/bugpoint.cc
index da06acedf..13cfca0e8 100644
--- a/passes/cmds/bugpoint.cc
+++ b/passes/cmds/bugpoint.cc
@@ -89,6 +89,10 @@ struct BugpointPass : public Pass {
 		log("    -updates\n");
 		log("        try to remove process updates from syncs.\n");
 		log("\n");
+		log("    -wires\n");
+		log("        try to remove wires. wires with a (* bugpoint_keep *) attribute will be\n");
+		log("        skipped.");
+		log("\n");
 		log("    -runner \"<prefix>\"\n");
 		log("        child process wrapping command, e.g., \"timeout 30\", or valgrind.\n");
 		log("\n");