boom
Here are 56 public repositories matching this topic...
Currently the COMMIT_LOG_PRINTF, MEMTRACE_PRINTF, and the DEBUG_PRINTF are executed as chisel prints which are emitted to stderr However you can only have one of these at a time, since they all go to stderr.
We should create C DPI widgets that also direct the logs into files. Preferably this would be some templated thing, since there are lots of things we potentially want to trace ou
-
Updated
Jul 7, 2020 - C
-
Updated
Jul 7, 2020 - JavaScript
Type definitions?
Any plan on mapping some TS type definitions for this package?
-
Updated
Jul 3, 2020 - C++
-
Updated
May 19, 2018 - Go
-
Updated
Feb 17, 2020 - JavaScript
-
Updated
Jul 6, 2020 - TypeScript
-
Updated
Aug 26, 2018 - Lua
-
Updated
Apr 16, 2019 - JavaScript
-
Updated
Jun 6, 2020 - C#
-
Updated
May 10, 2018 - JavaScript
-
Updated
Jul 20, 2018 - Java
Improve this page
Add a description, image, and links to the boom topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the boom topic, visit your repo's landing page and select "manage topics."
Tools such as
gofmtare very useful for quickly cleaning reformatting code according to some coding style. I think we need the same for Futhark. It's a bit more complicated to do this for an expression-oriented language than a statement-oriented one, but there is prior art we can look at (like Brittany for Haskell).While constructing
futhark fmti