Building SPEC CPU2006
https://developer.amd.com/wordpress/media/2012/10/building_speccpu.html
Building SPEC CPU2006
This file documents the use of the x86 Open64 Compiler Suite.
2009 Advanced Micro Devices, Inc.
Building SPEC CPU2006
CPU2006 is SPEC's current-generation processor benchmark suite that stresses a system's processor, memory subsystem and compiler. SPEC designed CPU2006 to provide a comparative measure of compute-intensive performance across the widest practical range of hardware using workloads developed from real user applications. These benchmarks are provided as source code and require the user to be comfortable using compiler commands as well as other commands via a command interpreter using a console or command prompt window in order to generate executable binaries. The current version of the benchmark suite is V1.1, released in June 2008. In order to build and run SPEC CPU2006, you will need to download the benchmark kit, install it, then build and test the component programs. These steps, and any known limitations, are described in the sections below.
The URL for the home page for this benchmark suite is SPEC CPU2006.
Download: In order to download the SPEC CPU2006 benchmarks, a license is required. An online order form can be found here. Once SPEC membership has been acquired, the benchmark kit can be downloaded from https://pro.spec.org/private/osg/cpu/cpu2006/src/cpu2006-1.1.tar.bz2. This site is password protected.
Installing the Kit
By convention, create a local directory on the system where you will build the benchmarks and run them called “CPU2006”. In that directory, excute the following commands:
>bzcat cpu2006-1.1.tar.bz2 | tar xvf –
>./install.sh
Enter “yes” to the prompt. Once complete, see the “Docs” subdirectory, which includes html format documentation on the SPEC harness and how to use it.
Building SPEC CPU2006
Building SPEC benchmarks is done using the SPEC harness. The first command to execute in the CPU2006 directory is:
>. ./shrc
This will set the value of the $SPEC environment variable to the directory CPU2006. The commands provided by the SPEC harness can be found in $SPEC/bin. Example configuration files can be found in $SPEC/config.
The configuration file is used to specify the compiler invocation command, libraries to be used, compiler flags for each benchmark, etc. This “config” file is also updated with MD5 checksums so that flag changes can be detected by the harness and benchmarks rebuilt only as needed. More information on how the MD5 checksums are used can be found in the SPEC documentation.
The documentation also describes the SPEC run and reporting rules. A “reportable” SPEC run is one that is suitable for submission to SPEC and eligible to be displayed on their results web pages. Reportable runs must follow strict requirements for documentation, MD5 checksums, and must run each individual benchmark program three times. However, it is also possible to do a non-reportable run with much less time and effort.
An example configuration file for building and running the SPEC benchmarks can be found in Example-open64.cfg. This file assumes the Barcelona microarchitecture and is configured for a single-core target run with no auto-parallelization. However, it is very similar to actual configuration files used for published SPEC results. You can issue the following command to build and run all of the SPEC benchmarks using this configuration file:
>runspec --loose --size=ref --iterations=1 --config=Example-open64 all
See the SPEC documentation for more details on the “runspec” command. Below is a variation of the above command which limits the building and running to a single named benchmark, and only using the BASE flags.
>runspec --loose --size=ref --iterations=1 --config=Example-open64 --tune=base perlbench
It is also possible to build the SPEC benchmarks without running them. Adding the option “—action=build” will build but not run the specified benchmarks.
It is also possible to “bundle” the resulting benchmark binaries and configuration file so they can be transported to a second system and executed there.
Please see the SPEC documentation for more details on these advanced features.
Known Limitations
There are no known limitations.
Building SPEC CPU2006的更多相关文章
- SPEC CPU2006的安装和使用
https://www.spec.org/download.html http://blog.lazzzy.xyz/2017/09/15/SPEC_CPU2006/ BenchMark SPEC CP ...
- spec cpu2006 官网
https://www.spec.org/cpu2006/Docs/install-guide-unix.html
- 【转载】]基于RedHatEnterpriseLinux V7(RHEL7)下SPEC CPU 2006环境搭建以及测试流程 介绍、安装准备、安装、config文件以及运行脚本介绍
https://www.codetd.com/article/1137423 <版权声明:本文为博主原创文章,未经博主允许不得转载> 本次利用SPECCPU2006测试工具来进行Intel ...
- 【转载】基于RedHatEnterpriseLinux V7(RHEL7)下SPEC CPU 2006环境搭建以及测试流程(之一)——介绍、安装准备、安装、config文件以及运行脚本介绍
基于RedHatEnterpriseLinux V7(RHEL7)下SPEC CPU 2006环境搭建以及测试流程(之一)--介绍.安装准备.安装.config文件以及运行脚本介绍 其他 2018-0 ...
- kvm 性能调优
CPU Tuning Cache share tuning 对于物理 CPU,同一个 core 的 threads 共享 L2 Cache,同一个 socket 的 cores 共享 L3 cache ...
- 转-4年!我对OpenStack运维架构的总结
4年!我对OpenStack运维架构的总结 原创: 徐超 云技术之家 今天 前言 应“云技术社区”北极熊之邀,写点东西.思来想去云计算范畴实在广泛,自然就聊点最近话题异常火热,让广大云计算从业者爱之深 ...
- 网易OpenStack部署运维实战
OpenStack自2010年项目成立以来,已经有超过200个公司加入了 OpenStack 项目,目前参与 OpenStack 项目的开发人员有 17,000+,而且这些数字还在增加,作为一个开源的 ...
- [转帖]你不曾见过的国产CPU:可能是最全的龙芯系列芯片家谱(下)
你不曾见过的国产CPU:可能是最全的龙芯系列芯片家谱(下) https://www.ijiwei.com/html/news/newsdetail?source=pc&news_id=7177 ...
- [知乎]这可能是最全面的龙芯3A3000处理器评测
这可能是最全面的龙芯3A3000处理器评测 第一千零一个人 已关注 蓬岸 Dr.Quest . https://zhuanlan.zhihu.com/p/50716952 这里面链接很全. 立党 ...
随机推荐
- Distributed | ZooKeeper
ZooKeeper与之前看的论文不太一样,它主要是描述了一个分布式协调服务,提供了wait-free的api,可以让用户自己设计要求更高的原语.通过Zab协议保证sever之间的一致性,同时让读请求在 ...
- 设计原则:单一职责(SRP)原则
1 什么是单一职责(SRP)原则 单一职责原则的英文是 Single Responsibility Principle,缩写为 SRP.翻译过来就是:一个类或者模块只负责完成一个职责(或者功能). 所 ...
- python进阶(一)变量与数据类型、python之禅
一.变量: 1.变量组成:由数据.字母与下划线组合 2.不能以数字开头 3.python关键字与函数名不能作为变量名 4.当字符串变量中包含引号时,可使用单引号与双引号进行区分,或转义 print(& ...
- Processing 状态机应用研究(线性转换)
状态机(State Machine)是一个抽象概念,是一个逻辑严谨的数学抽象.它的这种概念在现实生活中处处都有应用,或者说现实世界就充满状态机.要讨论状态机,就涉及到相关概念,比如:State 状态, ...
- 2020 OO 第四单元总结 UML
title: 2020 OO 第四单元总结 date: 2020-06-14 19:10:06 tags: OO categories: 学习 1. 本单元三次作业的架构设计 本单元的代码编写与第三单 ...
- Pyinstaller原理详解
Pyinstaller原理详解 什么是Pyinstaller Pyinstaller可以把Python程序打包成exe文件,可以在没有Python的电脑上运行,主要用于生产用. Python.h! 在 ...
- 【macOS】屏蔽Big Sur更新提示 消除更新红点
下面介绍如何屏蔽macOS系统更新,屏蔽Big Sur更新提示,消除更新红点. 取消自动更新选项 请选取苹果菜单 > "系统偏好设置",然后点按"软件更新&qu ...
- 【笔记】《Redis设计与实现》chapter9 数据库
9.1 服务器中的数据库 Redis服务器将所有都保存在服务器状态redis.h/redisServer结构中 struct redisServer{ //... // 一个数组,保存着服务器中所有数 ...
- Go 包管理与依赖查找顺序
目录 1. 规则: 2. 编译时的依赖包查找机制 3.vendor vendor的层级搜索 4. modules 1. 规则: 同一目录下只能存在一个包 目录和目录下源文件的包命名可以不同 当包名与目 ...
- I - 树的直径 POJ - 1383
The northern part of the Pyramid contains a very large and complicated labyrinth. The labyrinth is d ...