[ITK] Win64 Visual Studio 12 segfaults

[Niels Dekker]

Thanks for your reply, Bradley.

Are you sure that those 36 SimpleITK test failures are also caused by 
Win64 VS12 compiler bugs?  They don't seem to be caused by segfaults, 
whereas most of the 1296 test failures from 12 days ago were marked as 
SEGFAULT: 
https://open.cdash.org/viewTest.php?onlyfailed&buildid=3656652 
(Win64-vs12-shared-next, 2015-01-17).

I see many test failures from other compilers and architectures as 
well, at 
https://open.cdash.org/index.php?project=SimpleITK&date=2015-01-29 
Are these just SimpleITK issues?

If those 36 SimpleITK test failures are from another Win64 VS12 
compiler bug, I would be very interested to see a minimal example. You 
know, the segfault Win64 VS12 compiler bug can be reproduced by a 
program of just 10 lines of code, without any #include.  (As I 
commented at 
http://connect.microsoft.com/VisualStudio/feedbackdetail/view/1060166).

Any way, early next week we'll hope to submit our ITK patch. Maybe 
that also fix some of the SimpleITK issues...  :-)

   Kind regards, Niels

Bradley Lowekamp wrote on Jan. 29, 2015:
> I also have a SimpleITK build with Visual Studio 2013 (VS12)
> for SimpleITK for Win64 build against the ITK release branch:
> 2
> https://open.cdash.org/buildSummary.php?buildid=3671881
>
> It is down to 36 failures from 1287.  The CollidingFronts and
> FastMarchingUpwindGradient are SimpleITK issues.
>
> What's interesting is that there no report internal compiler error,
> with 64-bit ids enabled. We a bunch of Deconvolution filters
> failing put nothing else.
>
> Well this builds confidence in correct code being generated, I
> still would not give the generated code away to anyone and expect
> it to work 100%.
>
> I think we should likely add a CMake warning for this problematic
> compiler and architecture.