From 96c257c2738d8f60e42733c49a0ccb337cd2223a Mon Sep 17 00:00:00 2001
From: Maryam Tahhan <maryam.tahhan@intel.com>
Date: Wed, 12 Aug 2015 12:40:37 +0100
Subject: [PATCH] TestSpec: Add compiler details to test report info

Change-Id: I19d574607c29cbb8401047ab7d1255ba7282ef63
JIRA: VSPERF-47
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Eugene Snider <Eugene.Snider@huawei.com>
Reviewed-by: Gurpreet Singh <gurpreet.singh@spirent.com>
Reviewed-by: Tv Rao <tv.rao@freescale.com
---
 test_spec/vswitchperf_ltd.md | 1 +
 1 file changed, 1 insertion(+)
 mode change 100755 => 100644 test_spec/vswitchperf_ltd.md

diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md
old mode 100755
new mode 100644
index 51a493b0..96987567
--- a/test_spec/vswitchperf_ltd.md
+++ b/test_spec/vswitchperf_ltd.md
@@ -622,6 +622,7 @@ The starting point for defining the suite of tests for benchmarking the performa
     - Selected vSwitch, version number or commit id used.
       - vSwitch launch command line if it has been parameterised.
       - Memory allocation to the vSwitch – which NUMA node it is using, and how many memory channels.
+      - Where the vswitch is built from source: compiler details including versions and the flags that were used to compile the vSwitch.
     - DPDK or any other SW dependency version number or commit id used.
     - Memory allocation to a VM - if it's from Hugpages/elsewhere.
     - VM storage type: snapshot/independent persistent/independent non-persistent.
-- 
2.16.6