Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #1888

Closed
Open
Created Oct 22, 2017 by James Willenbring@jmwilleMaintainer

Document best practices for linking apps against Trilinos with CUDA

Created by: mhoemmen

@trilinos/framework @trilinos/tpetra

It looks like applications are not linking against Trilinos with CUDA in the way that Trilinos itself builds and links with CUDA. See discussion here: https://github.com/gahansen/Albany/issues/195

This suggests that Trilinos needs to document best practices for linking applications against Trilinos with CUDA. It could be that applications have multiple good options, in which case Trilinos should document the strengths and weaknesses of each.

Assignee
Assign to
Time tracking