@hackage clash-ghc1.8.2

Clash: a functional hardware description language - GHC frontend

  • Installation

  • Dependencies (42)

  • Dependents (5)

    @hackage/acme-everything, @hackage/clash-shake, @hackage/retroclash-sim, @hackage/clashilator, @hackage/retroclash-lib

    • Package Flags

      dynamic
       (off by default)

      Build Clash binaries with GHC flag `-dynamic`. This flag should only be used for packaging purposes. Installations using cabal should use `--enable-executable-dynamic`!

      use-ghc-paths
       (off by default)

      Locate the GHC core libraries using the `ghc-paths` package. Note: this flag may make binaries less relocatable, by hard-coding an absolute path to the core libraries.

      workaround-ghc-mmap-crash
       (off by default)

      Only use this flag when hit by GHC bug #19421. See clash-compiler PR #2444.

Clash is a functional hardware description language that borrows both its syntax and semantics from the functional programming language Haskell. The Clash compiler transforms these high-level descriptions to low-level synthesizable VHDL, Verilog, or SystemVerilog.

Features of Clash:

  • Strongly typed, but with a very high degree of type inference, enabling both safe and fast prototyping using concise descriptions.

  • Interactive REPL: load your designs in an interpreter and easily test all your component without needing to setup a test bench.

  • Higher-order functions, with type inference, result in designs that are fully parametric by default.

  • Synchronous sequential circuit design based on streams of values, called Signals, lead to natural descriptions of feedback loops.

  • Support for multiple clock domains, with type safe clock domain crossing.

This package provides:

  • Clash Compiler binary using GHC/Haskell as a frontend

Prelude library: https://hackage.haskell.org/package/clash-prelude