From b7e7d3cb049920e8602da3e468de3b0a81b8e9c0 Mon Sep 17 00:00:00 2001
From: Cary R <cygcary@yahoo.com>
Date: Tue, 13 May 2008 10:43:37 -0700
Subject: [PATCH] User tasks have empty nex_output().

This patch matches what is done in the development branch and
fixes the reported bug.
---
 net_nex_output.cc | 9 +++++++++
 netlist.h         | 1 +
 2 files changed, 10 insertions(+)

diff --git a/net_nex_output.cc b/net_nex_output.cc
index 7f7f919b9..6159b228a 100644
--- a/net_nex_output.cc
+++ b/net_nex_output.cc
@@ -159,6 +159,15 @@ void NetSTask::nex_output(NexusSet&out)
 {
 }
 
+/*
+* Consider a task call to not have any outputs. This is not quite
+* right, we should be listing as outputs all the output ports, but for
+* the purposes that this method is used, this will do for now.
+*/
+void NetUTask::nex_output(NexusSet&out)
+{
+}
+
 void NetWhile::nex_output(NexusSet&out)
 {
       if (proc_ != 0)
diff --git a/netlist.h b/netlist.h
index 06b0524bd..2d9b3d8eb 100644
--- a/netlist.h
+++ b/netlist.h
@@ -2465,6 +2465,7 @@ class NetUTask  : public NetProc {
       const NetScope* task() const;
 
       virtual NexusSet* nex_input(bool rem_out = true);
+      virtual void nex_output(NexusSet&);
       virtual bool emit_proc(struct target_t*) const;
       virtual void dump(ostream&, unsigned ind) const;