| Commit message (Collapse) | Author | Age | Files | Lines | 
| ... |  | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
By operating at a layer of abstraction over the rather clumsy Intel primitives,
we can avoid special hacks like `dffinit -highlow` in favour of simple techmapping.
This also makes the primitives much easier to manipulate, and more descriptive
(no more cyclonev_lcell_comb to mean anything from a LUT2 to a LUT6).
 | 
| |\  
| | 
| |  | 
ice40/ecp5: add support for both 1364.1 and Synplify/LSE RAM/ROM attributes
 | 
| | |  | 
 | 
| | |  | 
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
This commit tries to carefully follow the documented behavior of LSE
and Synplify. It will use `syn_ramstyle` attribute if there are any
write ports, and `syn_romstyle` attribute otherwise.
  * LSE supports both `syn_ramstyle` and `syn_romstyle`.
  * Synplify only supports `syn_ramstyle`, with same values as LSE.
  * Synplify also supports `syn_rw_conflict_logic`, which is not
    documented as supported for LSE.
Limitations of the Yosys implementation:
  * LSE/Synplify support `syn_ramstyle="block_ram,no_rw_check"`
    syntax to turn off insertion of transparency logic. There is
    currently no way to support multiple valued attributes in
    memory_bram. It is also not clear if that is a good idea, since
    it can cause sim/synth mismatches.
  * LSE/Synplify/1364.1 support block ROM inference from full case
    statements. Yosys does not currently perform this transformation.
  * LSE/Synplify propagate `syn_ramstyle`/`syn_romstyle` attributes
    from the module to the inner memories. There is currently no way
    to do this in Yosys (attrmvcp only works on cells and wires).
 | 
| | | 
| | 
| | 
| |  | 
LSE/Synplify use case insensitive matching.
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
This commit tries to carefully follow the documented behavior of LSE
and Synplify. It will use `syn_ramstyle` attribute if there are any
write ports, and `syn_romstyle` attribute otherwise.
  * LSE supports both `syn_ramstyle` and `syn_romstyle`.
  * Synplify only supports `syn_ramstyle`, with same values as LSE.
  * Synplify also supports `syn_rw_conflict_logic`, which is not
    documented as supported for LSE.
Limitations of the Yosys implementation:
  * LSE/Synplify appear to interpret attribute values insensitive
    to case. There is currently no way to do this in Yosys (attrmap
    can only change case of attribute names).
  * LSE/Synplify support `syn_ramstyle="block_ram,no_rw_check"`
    syntax to turn off insertion of transparency logic. There is
    currently no way to support multiple valued attributes in
    memory_bram. It is also not clear if that is a good idea, since
    it can cause sim/synth mismatches.
  * LSE/Synplify/1364.1 support block ROM inference from full case
    statements. Yosys does not currently perform this transformation.
  * LSE/Synplify propagate `syn_ramstyle`/`syn_romstyle` attributes
    from the module to the inner memories. There is currently no way
    to do this in Yosys (attrmvcp only works on cells and wires).
 | 
| |\ \  
| | | 
| | |  | 
"techmap -map +/cmp2lcu.v" for decomposing arithmetic compares to $lcu
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| |\ \ \  
| | | | 
| | | |  | 
IdString: use more ID::*, make them easier to use, speed up IdString::in()
 | 
| | | | |  | 
 | 
| | |/ /   | 
 | 
| |/ /  
| |   
| |   
| |   
| |   
| |    | 
This makes adding more FF types in the future much more manageable.
Fixes #1824.
 | 
| | |  | 
 | 
| |\ \  
| | | 
| | |  | 
ice40: Map unmapped 'mince' DFFs to gate level
 | 
| | | | 
| | | 
| | | 
| | |  | 
Signed-off-by: David Shah <dave@ds0.me>
 | 
| |/ /  
| |   
| |   
| |    | 
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
 | 
| | |  | 
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
According to the official simulation model, and also cross-checked
on real hardware, the data output of the SPRAM when chipselect is
low is kept stable. It doesn't go undefined.
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
 | 
| | |  | 
 | 
| |\ \  
| | | 
| | |  | 
ecp5: remove unused parameter from \$__ECP5_PDPW16KD
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| | | |  | 
 | 
| |\ \ \  
| | | | 
| | | |  | 
xilinx: cleanup DSP48E1 handling for abc9
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| |\ \ \ \  
| |/ / /  
|/| | |    | 
Add -flowmap option to `synth{,_ice40}`
 | 
| | | | |  | 
 | 
| |\ \ \ \  
| | | | | 
| | | | |  | 
abc9: auto-generate *.lut/*.box files and arrival/required times from specify entries
 | 
| | | | | |  | 
 | 
| | | | | |  | 
 | 
| | | | | |  | 
 | 
| | | | | |  | 
 | 
| | | | | |  | 
 |