Extra BDD nodes being created. Is this a bug?

From: Flavio M. De Paula (depaulfm_at_cs.ubc.ca)
Date: Tue May 30 2006 - 17:53:43 MDT

• Next message: Flavio M. De Paula: "Conditional branch in Verilog generating wrong BDD in VIS"
• Previous message: Aditya Kesiraju: "Vis installation problems on Solaris"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Hello fellow VIS users,

I noticed some weird behavior in VIS (Rel. 2.1) inital steps, ie, reading
  in the file, flattening the hierarchy, and building the mdds.

I get a different number of BDD nodes while calling 'write_order'
and by calling 'build_partition_mdds -s 2'

Intrigued by this behavior I decided to make a small change in VIS
such that when I call model_check it prints the pre-image minterms.

I noticed that the number of variables in the minterms are larger
than the reported in write_order matching what I noticed with the build_
partition_mdds command.

Well, I could not figure out where these extra BDD node variables
are coming from.

I am hoping some of you had experienced this befire or knows the
reason for this behavior.

I appreciate any help. I could also send out the Verilog code (more than
2000 lines of code) in case someone wants to take a closer look.

These are the steps I am following:

vis> read_blif_mv file.mv
vis> flatten_hierarchy
vis> static_order
vis> build_partition_mdds -s 2
vis> write_order

Thank you,
Flavio.

• Next message: Flavio M. De Paula: "Conditional branch in Verilog generating wrong BDD in VIS"
• Previous message: Aditya Kesiraju: "Vis installation problems on Solaris"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.7 : Tue May 30 2006 - 18:03:02 MDT