From 9176606044d27ef371642496410f9e4db17c7c81 Mon Sep 17 00:00:00 2001 From: Thomas Radke Date: Thu, 31 Mar 2005 08:22:00 +0000 Subject: CarpetSlab: pass vartype in comm_state constructor tto make use of collective communication buffers So far collective buffers can be used only for the collector object. For the case where all processors should receive the resulting hyperslab, the comm_state loop was left untouched because I didn't understand the code. darcs-hash:20050331082252-776a0-bae45b204fdf31f38969bee81c0ae97edae68f5c.gz --- Carpet/CarpetSlab/src/slab.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Carpet/CarpetSlab/src/slab.cc') diff --git a/Carpet/CarpetSlab/src/slab.cc b/Carpet/CarpetSlab/src/slab.cc index ac8ea0ef9..d204a1cca 100644 --- a/Carpet/CarpetSlab/src/slab.cc +++ b/Carpet/CarpetSlab/src/slab.cc @@ -209,7 +209,7 @@ namespace CarpetSlab { // Done with the temporary stuff mydata = 0; - for (comm_state state; !state.done(); state.step()) { + for (comm_state state(gp.vartype); !state.done(); state.step()) { // Loop over all components, copying data from them BEGIN_LOCAL_COMPONENT_LOOP (cgh, gp.grouptype) { -- cgit v1.2.3