<div class="gmail_quote">On Tue, Apr 24, 2012 at 13:17, Dave Goodell <span dir="ltr"><<a href="mailto:goodell@mcs.anl.gov">goodell@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Apr 24, 2012, at 1:04 PM CDT, Jed Brown wrote:<br>
<br>
> On Tue, Apr 24, 2012 at 12:57, Dave Goodell <<a href="mailto:goodell@mcs.anl.gov">goodell@mcs.anl.gov</a>> wrote:<br>
>><br>
</div><div class="im">>> Out of curiosity, how do you feel about just cheating a bit and using MPI_C_DOUBLE_COMPLEX for this particular use case? Do you believe the risk of some sort of mismatch between C's _Complex and std::complex to be too great?<br>
><br>
> We tried to do this, but learned that MPI_C_DOUBLE_COMPLEX was floating around in mpi.h just to trick our configure tests (since it fails at run-time on Windows) and the bug report was closed by you as INVALID.<br>
<br>
</div>Ahh, yes, the Windows-is-broken issue. Ignore me, I had paged this ticket out of my brain when writing the above email.</blockquote></div><br><div>So the "solution" is to not "fix" the Windows issue? ;-)</div>