This bugzilla service is closed. All entries have been migrated to https://gitlab.com/libeigen/eigen
Bug 1726 - Jacobi module does not compile on old NVCC / CUDA 6.5
Summary: Jacobi module does not compile on old NVCC / CUDA 6.5
Status: NEW
Alias: None
Product: Eigen
Classification: Unclassified
Component: Jacobi (show other bugs)
Version: 3.3 (current stable)
Hardware: x86 - 64-bit Linux
: Normal Compilation Problem
Assignee: Nobody
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-20 13:33 UTC by Caian Benedicto
Modified: 2019-12-04 18:41 UTC (History)
2 users (show)



Attachments

Description Caian Benedicto 2019-06-20 13:33:15 UTC
Hello, we are upgrading the Eigen version of our project from 3.2.9 to 3.3.7, but we are having problems compiling it in our target system, which is a legacy GCC 4.8.4 with CUDA 6.5:

> docker run \
>   -ti \
>   --rm \
>   --runtime=nvidia \
>   --volume="${PWD}:/source" \
>   --entrypoint=/bin/bash \
>   nvidia/cuda:6.5-devel-ubuntu14.04 \
>   -c 'cd /source && nvcc main.cu -I eigen-eigen-323c052e1731/'
> 
> eigen-eigen-323c052e1731/Eigen/src/Jacobi/Jacobi.h(455): error: expression > > must have a constant value
> 
> 1 error detected in the compilation of "/tmp/tmpxft_000000a5_00000000-4_main.cpp4.ii".

And here is an example that triggers the issue:

> #if !defined(__CUDA_ARCH__)
> #include <Eigen/Dense>
> #endif
> 
> #include <iostream>
> 
> int main(int argc, const char* argv[])
> {
>     return 0;
> }

This code does compile fine with Eigen 3.2.9, but not with the latest version. It is not intended to run on GPU, but still has to be preprocessed by NVCC as it is part of our library.

Thank you,

Caian
Comment 1 Nobody 2019-12-04 18:41:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to gitlab.com'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: https://gitlab.com/libeigen/eigen/issues/1726.

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