C/C++ Compiler Toolchain + BC + Bison + Flex + GNU Multiple Precision Arithmetic
* Uploading of benchmark result data to OpenBenchmarking.org is always optional (opt-in) via the Phoronix Test Suite for users wishing to share their results publicly. ** 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 current as of 17 October 2021.
pts/build-gdb-1.1.0 [View Source] Sat, 29 May 2021 07:13:45 GMT Update against GDB 10.2 upstream.
pts/build-gdb-1.0.1 [View Source] Sun, 09 Feb 2020 08:49:54 GMT Add makeinfo to SystemDependencies.
pts/build-gdb-1.0.0 [View Source] Sat, 08 Feb 2020 20:19:26 GMT Initial commit of GDB build test profile.
OpenBenchmarking.org metrics for this test profile configuration based on 460 public results since 29 May 2021 with the latest data as of 17 October 2021.
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 GDB GNU Debugger Compilation 10.2 - Time To Compile) has an average run-time of 5 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.1%.
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.