chiselX - Chisel with SFC compatibility

Age	Commit message (Collapse)	Author
2017-08-01	Address scalastyle issues, out of date comments, extraneous imports. (#658)	Jim Lawson
	No functional changes
2017-06-26	Directions internals mega-refactor (#617)	Richard Lin
	Part 1 of mega-change in #578 Major notes: - Input(...) and Output(...) now (effectively) recursively override their elements' directions - Nodes given userDirection (Input, Output, Flip - what the user assigned to _that_ node) and actualDirection (Input, Output, None, but also Bidirectional and BidirectionalFlip for mostly Aggregates), because of the above (since a higher-level Input(...) can override the locally specified user direction). - DataMirror (node reflection APIs) added to chisel3.experimental. This provides ways to query the user given direction of a node as well as the actual direction. - checkSynthesizable replaced with requireIsHardware and requireIsChiselType and made available in chisel3.experimental. Internal changes notes: - toType moved into Emitter, this makes the implementation cleaner especially considering that Vec types can't be flipped in FIRRTL. This also more clearly separates Chisel frontend from FIRRTL emission. - Direction separated from Bindings, both are now fields in Data, and all nodes are given hierarchical directions (Aggregates may be Bidirectional). The actualDirection at the Element (leaf) level should be the same as binding directions previously. - Bindings are hierarchical, children (of a, for example, Bundle) have a ChildBinding that points to their parent. This is different than the previous scheme where Bindings only applied at the Element (leaf) level. - Lots of small misc clean up. Future PRs will address other parts of #578, including stricter direction checks that aren't a side-effect of this internal refactor, stricter checks and splitting of binding operations (Wire vs. WireInit), and node operations not introduced here (getType and deprecation of chiselCloneType). Since those shouldn't mess with internals, those should be much smaller.
2017-04-13	Module Hierarchy Refactor (#469)	Richard Lin

2017-04-04	Define CompileOptions case class to support CompileOptions manipulation. (#572)	Jim Lawson
	Make it relatively easy to override a single CompileOption.
2016-11-21	Restyle a lot of test code, mainly with regex	ducky

2016-10-05	Give <> and := legacy behavior in compatibility mode	Andrew Waterman

2016-10-05	Make asInput/asOutput/flip deprecation warnings dynamic	Andrew Waterman
	Code that imports Chisel._ shouldn't see them. Not sure if requireIOWrap is the right condition... or if cyan is a good choice of color for deprecation warnings.
2016-09-29	Consolidate CompileOptions and re-enable NotStrict pending macro work.	Jim Lawson

2016-09-29	Massive rename of CompileOptions.	Jim Lawson
	Massage CompileOption names in an attempt to preserve default (Strict) CompileOptions in the absence of explicit imports. NOTE: Since the default is now strict, we may encounter errors when we generate connections for clients (i.e., in Vec.do_apply() when we wire up a sequence). We should really thread the CompileOptions through the macro system so the client's implicits are used.
2016-09-06	Verify we can suppress the inclusion of default compileOptions.	Jim Lawson

2016-09-01	Move connection implicits from Module constructor to connection methods.	Jim Lawson
	Eliminate builder compileOptions.
2016-08-30	Add example of specific CompileOptions settings to tests.	Jim Lawson

2016-08-30	Add abstract classes with explicit connection checking options.	Jim Lawson

2016-08-29	Check module-specific compile options.	Jim Lawson
	Import chisel3.NotStrict.CompileOptions in Chisel package. Add CompileOptions tests.