This bugzilla service is closed. All entries have been migrated to

Bug 388

Summary: Runtime failure in 'evalutors' test on 3.1.0-alpha1 using Intel 11.1
Product: Eigen Reporter: Rhys Ulerich <rhys.ulerich>
Component: Core - expression templatesAssignee: Nobody <eigen.nobody>
Severity: Failed Unit Test CC: chtz, gael.guennebaud, jacob.benoit.1, jitseniesen
Priority: Normal    
Version: 3.3 (current stable)   
Hardware: x86 - 64-bit   
OS: Linux   
Bug Depends on:    
Bug Blocks: 99    

Description Rhys Ulerich 2011-12-07 17:14:44 UTC
Using on
Intel 11.1 I see a runtime failure in
       513 - evaluators (Failed)
The same test works fine for G++ 4.5.1.  Details on the failing
configuration follow.

- Rhys

-- ************************************************************
-- ***    Eigen's unit tests configuration summary          ***
-- ************************************************************
-- Build type:        Release
-- Build site:        setun
-- Build string:      linux-2.6.32-31-generic-g++icpc (icc) 11.1 20100806
copyright (c) 1985-2010 intel corporation.  all rights reserved.-32bit
-- Enabled backends:  Cholmod,  UmfPack,  Qt4 support,  fftw,  OpenGL,  GSL,
-- Disabled backends: SuperLU,  GoogleHash,  Adolc,  MPFR C++,
-- Default order:     Column-major
-- Maximal matrix/vector size: 320
-- SSE2:              Using architecture defaults
-- SSE3:              Using architecture defaults
-- SSSE3:             Using architecture defaults
-- SSE4.1:            Using architecture defaults
-- SSE4.2:            Using architecture defaults
-- Altivec:           Using architecture defaults
-- ARM NEON:          Using architecture defaults
Comment 1 Rhys Ulerich 2011-12-07 17:19:41 UTC
Notice this is at -O3.  Not sure what optimization level is supported for Intel.  Feel free to tell me to re-run it at -O2 if you like.
Comment 2 Jitse Niesen 2011-12-12 18:34:18 UTC
While this of course needs to be fixed eventually, evaluators will not make it into 3.1. Would it make sense to disable this test for 3.1, or even remove this file and AssignEvaluator.h and CoreEvaluators.h temporarily and resurrect them when we branch 3.2? It could be quite confusing if we include code in Eigen 3.1 that isn't used anywhere.
Comment 3 Benoit Jacob 2011-12-12 18:46:12 UTC
Sounds like a plan.
Comment 4 Gael Guennebaud 2011-12-12 19:00:33 UTC
I agree with that too
Comment 5 Gael Guennebaud 2012-06-22 09:40:45 UTC
I resurrected the changes:
changeset:   0621fc0573b5
user:        ggael
date:        2012-06-22 09:39:35
summary:     resurrect expression evaluators
Comment 6 Christoph Hertzberg 2015-03-08 06:47:41 UTC
This unit test has been passing successfully for a while now.
Comment 7 Nobody 2019-12-04 11:18:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: