From 1325a3e2b64e4620cd094cefcda5f71a7a50ddc6 Mon Sep 17 00:00:00 2001
From: steve <steve>
Date: Tue, 1 Aug 2000 21:32:40 +0000
Subject: [PATCH]  Use the iverilog command in documentation.

---
 xnf.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/xnf.txt b/xnf.txt
index dad4d1c09..e83ff0274 100644
--- a/xnf.txt
+++ b/xnf.txt
@@ -15,7 +15,7 @@ GENERATE XNF OUTPUT -- THE SHORT STORY
 The easiest way to compile for XNF output is with the "verilog"
 command (man verilog) and the -X switch:
 
-	% verilog -fpart=4010e -fncf=prog.ncf -X prog.v
+	% iverilog -fpart=4010e -fncf=prog.ncf -txnf prog.v
 
 This generates from the prog.v Verilog source file the prog.xnf output
 and the prog.ncf netlist constraints file. The verilog program
@@ -245,6 +245,9 @@ IBUF, NOT gates cannot be absorbed as in the OPAD case.
 
 
  $Log: xnf.txt,v $
+ Revision 1.14  2000/08/01 21:32:40  steve
+  Use the iverilog command in documentation.
+
  Revision 1.13  2000/08/01 02:48:42  steve
   Support <= in synthesis of DFF and ram devices.