From 1435931cd6b6239b921649ead1aa1c1c9c9d2f99 Mon Sep 17 00:00:00 2001 From: Henning Baldersheim Date: Sat, 6 May 2017 09:54:24 +0000 Subject: Due to c++17 eval order in gcc 7 we need to be more careful. From gcc 7 release notes. "The C++17 evaluation order requirements can be selected in other modes with the -fstrong-eval-order flag, or disabled in C++17 mode with -fno-strong-eval-order." --- vdslib/src/vespa/vdslib/distribution/group.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'vdslib') diff --git a/vdslib/src/vespa/vdslib/distribution/group.cpp b/vdslib/src/vespa/vdslib/distribution/group.cpp index b1a81c85dbb..8ad3dcb2f80 100644 --- a/vdslib/src/vespa/vdslib/distribution/group.cpp +++ b/vdslib/src/vespa/vdslib/distribution/group.cpp @@ -116,7 +116,8 @@ Group::addSubGroup(Group::UP group) "Another subgroup with same index is already added.", VESPA_STRLOC); } - _subGroups[group->getIndex()] = group.release(); + auto index = group->getIndex(); + _subGroups[index] = group.release(); } void @@ -203,4 +204,4 @@ Group::getDistributionConfigHash() const { } } -} \ No newline at end of file +} -- cgit v1.2.3