1. Apr 20, 2021
  2. Apr 16, 2021
  3. Apr 15, 2021
  4. Apr 13, 2021
  5. Apr 08, 2021
  6. Apr 01, 2021
  7. Mar 30, 2021
  8. Mar 27, 2021
  9. Mar 24, 2021
  10. Mar 19, 2021
    • Jack Koenig's avatar
      Update the FAQ and add doc on versioning (#1827) · 03ec2156
      Jack Koenig authored
      
      
      * Update the FAQ and add doc on versioning
      * Update modules.md
      
      Co-authored-by: default avatarMegan Wachs <megan@sifive.com>
      03ec2156
    • Megan Wachs's avatar
      Reorganize website docs (#1806) · f1ad5b58
      Megan Wachs authored
      Updates to chisel3 documentation for website:
      * guard code examples with mdoc and fix errors encountered along the way
      * move some website content here vs splitting the content across two repos
      * Bring in the interval-types and loading memories content so that it will be visible from the website
      * remove all references to the wiki (deprecated)
      * Remove reference to Wiki from the README
      * fix tabbing and compile of chisel3-vs-chisel2 section
      * Appendix: faqs now guarded and compile
      * FAQs: move to resources section
      f1ad5b58
    • Boyang Han's avatar
    • Schuyler Eldridge's avatar
      Don't toggle top.cpp clock and reset on same cycle (#1820) · ac094a5e
      Schuyler Eldridge authored
      
      
      Change top.cpp to deassert reset one time unit before the clock asserts.
      This avoids a Verilator simultation issue in top.cpp where the eval()
      function is only called once per simultation loop.  If the clock and
      reset are both changed and eval() is only called once, then any
      combinational update due to a change in reset is not visible to the
      sequential logic.  This avoids issues where the downstream compilation
      utilities move synchronous reset logic outside of an always block that
      describes a synchronous reset flip flop.
      
      Reset now deasserts on time unit 10 and the clock ticks on time unit
      11.
      
      h/t @albert-magyar
      
      Signed-off-by: default avatarSchuyler Eldridge <schuyler.eldridge@sifive.com>
      ac094a5e
  11. Mar 18, 2021
  12. Mar 16, 2021
  13. Mar 13, 2021
  14. Mar 12, 2021
  15. Mar 04, 2021
  16. Mar 03, 2021
  17. Mar 02, 2021
  18. Feb 27, 2021
  19. Feb 24, 2021
  20. Feb 11, 2021
    • Schuyler Eldridge's avatar
      Fix stack trace trimming across Driver/ChiselStage (#1771) · 2b5466c7
      Schuyler Eldridge authored
      
      
      * Handle MemTypeBinding in Analog
      
      Signed-off-by: default avatarSchuyler Eldridge <schuyler.eldridge@sifive.com>
      
      * Fix stack trace trimming across ChiselStage
      
      Fix bug in stack trace trimming behavior. Now, the following is what
      happens:
      
      1. The Builder, if catching accumulated errors, will now throw a
         ChiselException with a Scala-trimmed Stack trace. Previously, this
         would throw the full excpetion.
      2. The Elaborate phase handles stack trace trimming. By default, any
         Throwable thrown during elaboration will have its stack
         trace *mutably* trimmed and is rethrown. A logger.error is printed
         stating that there was an error during elaboration and how the user
         can turn on the full stack trace. If the --full-stacktrace option
         is on, then the Throwable is not caught and only the first
         logger.error (saying that elaboration failed) will be printed.
      3. ChiselStage (the class), ChiselStage$ (the object), and ChiselMain
         all inherit the behavior of (2).
      
      Mutable stack trace trimming behavior is moved into an implicit
      class (previously this was defined on ChiselException only) so this
      can be applied to any Throwable.
      
      No StageErrors are now thrown anymore. However, StageErrors may still
      be caught by ChiselMain (since it is a StageMain).
      
      Testing is added for ChiselMain, ChiselStage, and ChiselStage$ to test
      all this behavior.
      
      Signed-off-by: default avatarSchuyler Eldridge <schuyler.eldridge@sifive.com>
      2b5466c7
    • Jack Koenig's avatar
      Merge pull request #1624 from chipsalliance/gc-data · f41e7628
      Jack Koenig authored
      Make Data GC-able
      f41e7628
  21. Feb 10, 2021
    • Jack Koenig's avatar
      Make it possible to GC Data instances · 0a0d7c6a
      Jack Koenig authored
      No longer create a pointer from parent to every HasId, only do it by
      default for BaseModules and MemBases. Add pointer from parent to Data
      upon binding the Data.
      
      * Add MemTypeBinding for port types of Mems
      
      This binding is similar to the SampleElementBinding for Vecs in that
      these Data are not truly hardware, but are represented in the FIRRTL IR
      and thus need some representation.
      
      * Call _onModuleClose on unbound Records
      
      This maintains some corner-case behavior that is nevertheless relied
      upon. It ensures that refs are set for the elements of Records, even if
      they are not bound to any real hardware.
      0a0d7c6a
    • Jack Koenig's avatar
      Add no-plugin-tests for testing Chisel without the compiler plugin · 53b62047
      Jack Koenig authored
      This is a new SBT build unit that symlinks in some files from the normal
      chisel project tests, but builds them without the compiler plugin.
      53b62047
  22. Feb 09, 2021
  23. Feb 06, 2021
  24. Feb 05, 2021
    • Jack Koenig's avatar
      Minor docs improvements (#1774) · 8fa46071
      Jack Koenig authored
      * Fix some botched formatting (replace ```mdoc scala with ```scala mdoc)
      * Replace some unnecessary uses of triple backticks with single
        backticks
      * Move appendix docs from wiki-deprecated/ to appendix/
        * This will require an update on the website as well
      * Update Bundle literal docs
      8fa46071
  25. Feb 04, 2021
  26. Feb 02, 2021
  27. Jan 27, 2021