if given range can't be fully represented with specified precision, round to nearest relevant given open/closed info -- this is in creating intervals. Consider rethinking for anywhere IntervalRange is used

chisel doesn't pass open/closed-ness of ranges to firrtl with asInterval. Need to deal with ahead of time when bp + bounds are known. How about when they're not known?

revert old changes causing fp/interval lits to be incorrect (width wrong); corrected some interval related bounds (or made unknown) in IR

fix or remove some incorrect interval propagation in class Interval; also fixed some incorrect methods

.setBinaryPoint(that: Int)
.shiftLeftBinaryPoint(that: Int)
.shiftRightBinaryPoint(that: Int)
@azidar, please review

Added tests, which don't have any obvious errors

Added wrap(that: IntervalRange) API

Create generic wrap and clip methods that convert to UnknownBounds until
I can talk to Adam and figure out what I should do.
Add support for generating clip and wrap in Chirrtl

Tests forthcoming

Add a few tests for these.

This was because Range bases its width calculation on SInt bit
requirements

fix width check bug for negative FP and Interval lits -- SLit width check would fail after unsigned conversion. Width check wanted more bits than was necessary.

All inference at chisel level for now just returns
fully undetermined IntervalRange.  This should be made better after
we have more things working

Working on IntervalSpec now
Implemented + for Interval
Now problem with asInterval in firrtl compiler

Many changes. Time to start testing

IntervalRange is wrapper class for firrtl IntervalType