path: root/tools
diff options
authorSachin Gupta <>2016-07-18 09:06:27 -0500
committerSachin Gupta <>2016-07-20 23:18:11 -0400
commita058c58733a6f15387cb95fd0ed3823ede85b4ad (patch)
treeb3742674a2c4a5cf29a5abc1c7ce7bc6ebed7a7e /tools
parente70b411e5a0c3f2ee876149d6e56dea7a2902f6a (diff)
Allowing compilation if there is hash collision in same file.
This is in sync with the approach we use when there is hash collision across files. As we are using mirroring, sometime its not possible to fix hash collision for a commit immidiately. So allowing compilation and expecting to fix hash collision separately. Change-Id: Ibe3a5e6ab9352e7512fecf4aef993e8f3458176c Reviewed-on: Reviewed-by: Gregory S. Still <> Reviewed-by: Santosh S. Puranik <> Tested-by: Jenkins Server <> Reviewed-by: Shakeeb A. Pasha B K <> Reviewed-by: Sachin Gupta <>
Diffstat (limited to 'tools')
1 files changed, 5 insertions, 1 deletions
diff --git a/tools/ppetracepp/ppetracepp.C b/tools/ppetracepp/ppetracepp.C
index 5cd7a2ff..5f86a60b 100755
--- a/tools/ppetracepp/ppetracepp.C
+++ b/tools/ppetracepp/ppetracepp.C
@@ -431,7 +431,11 @@ void parse_line(map<string,string>& rhash, string& line, string& out_line)
fprintf(stderr, "hash collision: two different strings give the same hash value '%s'\n", hash32.c_str());
fprintf(stderr, "%s\n%s\n", strings.c_str(), rhash[hash32].c_str());
- return;
+ // Not breaking the compilation here. This is same as if we get hash
+ // collision across files. As in SBE we are using mirroring, these
+ // hash collisions will take some time to resolve. Till that time,
+ // let us allow compilation of procedures.
+ //return;
rhash[hash32] = strings;
OpenPOWER on IntegriCloud