This bugzilla service is closed. All entries have been migrated to
Bug 1556 - heap corruptions for some tests using clang-cl on windows
Summary: heap corruptions for some tests using clang-cl on windows
Status: NEW
Alias: None
Product: Eigen
Classification: Unclassified
Component: Tests (show other bugs)
Version: 3.4 (development)
Hardware: x86 - 64-bit Windows
: Normal Failed Unit Test
Assignee: Nobody
Depends on:
Reported: 2018-06-14 13:30 UTC by Marius Guggenmos
Modified: 2019-12-04 17:42 UTC (History)
3 users (show)


Description Marius Guggenmos 2018-06-14 13:30:18 UTC
I am trying to compile the tests of eigen 3.3.4 on windows 10 with clang-cl release 6.0 for x86_64.

eigen source:
llvm binary:

The .bat script to build the tests can be found here
It requires ninja, cmake and visual studio build tools and you might need to adjust the path to the visual studio command prompt/clang-cl binary to use it.
Simply put the content into a .bat file in the same directory as the extracted eigen source code and run it (preferably using powershell).

The failing tests are: basicstuff_3 basicstuff_5 basicstuff_7 block_3 block_5 block_6

It only fails for 64 bit and works for 32 bit.
The behavior is different depending on the build type:
Debug: everything works
Release: only block_3 block_5 block_6 fail
RelWithDebInfo: all of the listed tests fail
Sample output of compilation + testing with RelWithDebInfo:

When compiling with the msvc compiler it works (can be tested by commenting out the set CC and set CXX lines)

I am not sure if clang is supported on windows but figured I try reporting it anyway since firefox and chrome use it on windows for their builds, so it is most likely here to stay. I am not sure whether this is an issue with eigen or with clang on windows though.
Comment 1 Nobody 2019-12-04 17:42:40 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:

Note You need to log in before you can comment on or make changes to this bug.