Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • elpa elpa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • elpa
  • elpaelpa
  • Issues
  • #66
Closed
Open
Issue created Apr 17, 2019 by Andreas Marek@amarekOwner

ELPA changes the number of the OpenMP threads, even for calling program

When ELPA, e.g. in the autotuning, changes the number of OpenMP threads this is done globally. But this also affects the calling program.

To cure this, the original number of threads should be stored, and at the end of ELPA restored

Assignee
Assign to
Time tracking