Timed Clash Compilation
Build the clash-lang Haskell to VHDL/Verilog/SystemVerilog compiler with GHC 8.10.1
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark build-clash.
Project Site
clash-lang.orgTest Created
4 June 2020Last Updated
28 November 2020Test Maintainer
Serge KosyrevTest Type
ProcessorAverage Install Time
8 Minutes, 27 SecondsAverage Run Time
57 Minutes, 37 SecondsTest Dependencies
CurlAccolades
20k+ DownloadsSupported Platforms
** Data based on those opting to upload their test results to OpenBenchmarking.org and users enabling the opt-in anonymous statistics reporting while running benchmarks from an Internet-connected platform.
*** Test profile page view reporting began March 2021.
Data updated weekly as of 21 November 2024.
Suites Using This Test
Performance Metrics
Analyze Test Configuration:Timed Clash Compilation
Time To Compile
OpenBenchmarking.org metrics for this test profile configuration based on 393 public results since 4 June 2020 with the latest data as of 16 May 2024.
Below is an overview of the generalized performance for components where there is sufficient statistically significant data based upon user-uploaded results. It is important to keep in mind particularly in the Linux/open-source space there can be vastly different OS configurations, with this overview intended to offer just general guidance as to the performance expectations.
Based on OpenBenchmarking.org data, the selected test / test configuration (Timed Clash Compilation - Time To Compile) has an average run-time of 19 minutes. By default this test profile is set to run at least 3 times but may increase if the standard deviation exceeds pre-defined defaults or other calculations deem additional runs necessary for greater statistical accuracy of the result.
Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 0.6%.
Does It Scale Well With Increasing Cores?
No, based on the automated analysis of the collected public benchmark data, this test / test settings does not generally scale well with increasing CPU core counts. Data based on publicly available results for this test / test settings, separated by vendor, result divided by the reference CPU clock speed, grouped by matching physical CPU core count, and normalized against the smallest core count tested from each vendor for each CPU having a sufficient number of test samples and statistically significant data.
Tested CPU Architectures
This benchmark has been successfully tested on the below mentioned architectures. The CPU architectures listed is where successful OpenBenchmarking.org result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.