RE: [eigen] Problems compiling 3.0.2 tests on VS2008

["Schmidt, Michael" <Michael.Schmidt@xxxxxxxxxxxxxxxxxxx>]

I built the complete "buildtests" project using VS 2008 again and attached the output of running all the problematic builds to this mail (zipped in order to maintain reasonable attachment size). The following tests all exit with the Internal Compiler Error in line 578 of eigen\src\core\products\generalblockpanelkernel.h:

adjoint_4
basicstuff_6
cholesky_6
determinant_5
dontalign_7
dontalign_8
eigensolver_complex_2
eigensolver_generic_2
eigensolver_selfadjoint_5
eigensolver_selfadjoint_9
geo_hyperplane_4
hessenberg_5
householder_6
inverse_6
jacobisvd_1
jacobisvd_8
lu_5
lu_6
matrix_exponential_1
matrix_exponential_2
matrix_exponential_3
matrix_exponential_4
matrix_exponential_5
matrix_exponential_6
matrix_function_1
matrix_function_2
matrix_function_3
matrix_function_4
matrix_function_5
matrix_function_6
matrix_function_7
mixingtypes_3
permutationmatrices_7
product_extra_3
product_extra_4
product_large_4
product_mmtr_3
product_mmtr_4
product_notemporary_3
product_notemporary_4
product_symm_3
product_symm_4
product_syrk_3
product_syrk_4
product_trmm_3
product_trmm_4
product_trsolve_3
product_trsolve_4
qr_2
qr_7
qr_8
qr_colpivoting_3
qr_colpivoting_6
qr_fullpivoting_3
qr_fullpivoting_4
schur_complex_2
sparse_ldlt_2
sparse_llt_2
sparse_product_2
sparse_solvers_2
triangular_4
triangular_5

Furthermore, some tests just need really long compile times (several minutes), such as geo_transformations_2/3/6 and small_product_5. For basicstuff_6 the compile time is so long, that I somewhen killed the process. Are such long compile times to be expected?

Best, Michael 

 
-----Original Message-----
From: Listengine [mailto:listengine@xxxxxxxxxxxxxxxxx] On Behalf Of Schmidt, Michael
Sent: Montag, 12. September 2011 16:46
To: eigen@xxxxxxxxxxxxxxxxxxx
Subject: RE: [eigen] Problems compiling 3.0.2 tests on VS2008

Yes, a new release with working test suite would be nice. However, after having fixed the min/max things locally (I can provide a patch if you like) I now face another problem: My Visual Studio 2008 SP1 exits with internal compiler errors for quite some tests when I try to compile them in the "Release|x64" mode, for example the triangular_5 test. Attached to this mail, you can find the output of VS 2008 for this project. Right now, I am trying to compile the full test suite again to see which tests fail. Interestingly, the triangular_5 test fails for all 3.0 releases. Does anybody else encounter such problems? In Debug mode and in 32bit mode, the tests compile fine.... 

Regards, Michael

-----Original Message-----
From: Listengine [mailto:listengine@xxxxxxxxxxxxxxxxx] On Behalf Of Benoit Jacob
Sent: Sonntag, 11. September 2011 15:28
To: eigen@xxxxxxxxxxxxxxxxxxx
Subject: Re: [eigen] Problems compiling 3.0.2 tests on VS2008

We should release 3.0.3 with this fix, shouldn't we?

Benoit

2011/8/30 Schmidt, Michael <Michael.Schmidt@xxxxxxxxxxxxxxxxxxx>:
> Dear all,
>
>
>
> I just tried to compile the Eigen-Tests for the 3.0.2 tag and I got 
> compilation errors for about 100 out of the ~550 tests. I didn't read 
> all of them, but at least the majority seems to be related to the use 
> of min/max macros, like this one:
>
>
>
> 14>..\..\eigen3.0\test\sparse_basic.cpp(36) : error C2039:
> 'please_protect_your_max_with_parentheses' : is not a member of 'std'
>
> 14>        ..\..\eigen3.0\test\sparse_basic.cpp(277) : see reference 
> 14>to
> function template instantiation 'void
> sparse_basic<Eigen::SparseMatrix<_Scalar>>(const SparseMatrixType &)' 
> being compiled
>
> 14>        with
>
> 14>        [
>
> 14>            _Scalar=std::complex<double>,
>
> 14>            
> 14>SparseMatrixType=Eigen::SparseMatrix<std::complex<double>>
>
> 14>        ]
>
> 14>..\..\eigen3.0\test\sparse_basic.cpp(36) : error C2065:
> 'please_protect_your_max_with_parentheses' : undeclared identifier
>
>
>
> As far as I can see, these errors are fixed in the tip version already (e..g.
> in the aforementioned sparse_basic.cpp) but NOT in the 3.0.2 branch. 
> Is it possible that there was some kind of an incomplete merge to the 3.0 branch?
> I'm not very familiar with Mercurial yet, so I have some difficulties 
> follow all the commits/merges.
>
>
>
> Best regards, Michael

Attachment: build.zip
Description: build.zip