Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • eigen eigen
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 681
    • Issues 681
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libeigenlibeigen
  • eigeneigen
  • Issues
  • #1462
Closed
Open
Issue created Dec 04, 2019 by Eigen Bugzilla@eigenbzReporter

__CUDACC_VER__ is deprecated in CUDA 9

Submitted by Pieter Noordhuis

Assigned to Nobody

Link to original bugzilla bug (#1462)
Platform: GPU (CUDA)

Description

In the recently released CUDA 9 RC, the CUDACC_VER macro is deprecated. It is set to an error string, so it will cause compilation errors. The recommended macro's to use are CUDACC_VER_MAJOR, CUDACC_VER_MINOR, and CUDACC_VER_PATCH.

I worked around this problem by #undef'ing the error string macro and resetting it to behave as it previously did. Ideally this is addressed in Eigen itself though.

I verified this is a problem in 3.3, but see the macro is still used in trunk.

https://github.com/facebookincubator/gloo/commit/0c9766691d77eb54c5a3293bc29621a82424fabb

Edited Dec 05, 2019 by Eigen Bugzilla
Assignee
Assign to
Time tracking