1. Feb 21, 2018
  2. Feb 17, 2018
  3. Feb 16, 2018
  4. Feb 14, 2018
  5. Feb 09, 2018
  6. Feb 03, 2018
  7. Jan 31, 2018
  8. Jan 29, 2018
  9. Jan 28, 2018
  10. Jan 25, 2018
    • Richard Xia's avatar
      Remove unused BuildInfo.BuildTime. (#766) · 639617ea
      Richard Xia authored
      BuildInfo.BuildTime appears to cause sbt to always recompile BuildInfo to get
      the latest time, which causes a recompile on any package that depends on
      chisel3. This is quite painful for doing development on any Chisel projects.
      BuildTime doesn't actually appear to be in use, and removing it fixes the
      unnecessary recompilation issue.
      639617ea
  11. Jan 24, 2018
    • Richard Lin's avatar
      Runtime API deprecation warnings (#761) · 224740ac
      Richard Lin authored
      Add runtime warnings for use of deprecated Chisel methods. This is done using a macro that takes the message from a `@deprecated` annotation, and adds a call to `Builder.deprecated`.
      
      Reasoning is that by default, Scala doesn't print all deprecations, and that it's somewhat tricky to notice them - yet some support questions revolve around the use of deprecated and terribad API. This now prints warnings for uses of deprecated functions at runtime, and aggregates them by error and line to avoid spam. Also included is convenient information on enabling scalac deprecations.
      
      This also changes how line numbers for Chisel's error facility is determined, using prefix string comparison of the stack trace element classnames, instead of checking if the class is a subtype of UserModule. The previous one (specifically, calls to Class.forName) seems to interact badly with reflection-based cloneType when called at scale. This should also give more accurate reporting of errors that are in user code but outside of a UserModule.
      
      It turns out that `@deprecated` on macro functions don't do anything, so this changes the tags to the functions that the macros point to, which seems to work properly. It also turns out that there's a bunch of uses of deprecated functions in chiselTests which needs to be fixed.
      
      Not all `@deprecated` functions are also annotated with `@chiselRuntimeDeprecation`, because they're still used in Chisel internals, and we can't track whether they're called by the user or by Chisel and it will give a misleading error. These are a small amount of functions.
      224740ac
  12. Jan 20, 2018
  13. Jan 19, 2018
  14. Jan 17, 2018
  15. Jan 03, 2018
  16. Dec 23, 2017
  17. Dec 22, 2017
  18. Dec 21, 2017