Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK-m VTK-m
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 194
    • Issues 194
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTK-mVTK-m
  • Issues
  • #680
Closed
Open
Created Feb 09, 2022 by Vicente Bolea@vbolea💬Maintainer

Allow specifying a concrete CUDA arch

Currently we set the wanted CUDA arch (virtual/physical) by setting up VTKm_CUDA_Architecture to the specified Architecture generation (Pascal, Maxwell...). In many cases when we specify the CUDA arch in VTK-m, it will internally enable more than one specific architecture of the same arch generation.

This is normally useful since we can give every bit of optimizations for each GPU pertaining to the same generation. On the other hand it also results in a size increase of the VTK-m binaries.

We need to give the users a way to specify a single CUDA arch for wish they wish their VTK-m build be built with.

cc @cyrush1

Assignee
Assign to
Time tracking