BUG #   DESCRIPTION                                             WORKAROUND
-------------------------------------------------------------------------------------
09501   Many times designers define a size parameter as in      Replace `SZ-1 with 3!
         "`define SZ 4" thendeclare: reg [`SZ-1:0] r;
        This causes a problem, due to the expression `SZ-1.
09502   "FatalError 6: Internal error in file  ...UCase.cpp 	Fixed in next patch.
        line 89! Please notify developper with relevant input 
  	and trace!"
09503   Assigning to a concatenation expr (i.e. the LHS is a 	Fixed in next patch.
        concat) is not supported. Instead of a relevant error 
	msg, you get something about initialization of some 
	sort.
09504   A problem when using bitwise XOR.       		Fixed in next patch.
09505   Performance problem: Vapor runs slow when there is an 	
	expression with big number of binary operators. For 
        example: a = a1&&a2&&a3&&a4&&a5&&..
        This expression is represented in the front-end by a
	number of binary &&'s as in: (((a1&&a2)&&a3)&&a4)...
	This might slow down Vapor.
09506	You have to run 'vaporize' while in the bin/ directory.
	Also, if it complains about 'ivl not found' then make
	sure your $PATH includes "." in it.
09507	A process with no signals in the sensitivity list is
	supposed to combinational logic. In some cases it is
	interpreted as sequential. This is under debugging right
	now, and is not expetced to be anything serious!
09508	Do not apply selection on a term that interfaces with
	a memory module. Clone it to a new wire, and with the
	new wire you are free to go!
09509	DEFV is buggy when used with a 1-bit signal.		None for the moment.
								Try to avoid it!
09510	Vapor injects flushing and projecting to the statements	Fixed in next patch.
	of the PC, stall signal, and others. There is a bug for
	this case when the signal is originally conditioned (if
	statement in the code).
09511   FatalError 16: Module * was not found! This is likely   Make sure all your verilog
        a preprocessing problem (e.g. flattening).... 		files end with a new line.
09512	Bug in the flattener when x or z values are used.	Fixed in next patch
09513	When using the contants threshold, Vapor defines 	Fixed in next patch
	constants as general terms that are not related to
	UCLID_CONST_0. To prevent false negatives, however,
	these should be consistent across the various statements
	of the module, and across different modules as well.
	The current version does not insure that.
09514	The tool should not allow assignments with inconsistent	Done in next patch
	bit-vector width.