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
  • #42
Closed
Open
Issue created Jan 25, 2017 by Andreas Marek@amarekOwner

Code divergence of real/complex CPU part in trans_ev_band_to_full

The real/complex CPU parts of trans_ev_band_to_full diverged:

The real code path uses blocking, the complex part does not!

To do:

  • make blocking in real part an OPTION, i.e. a fall back to same code path as the complex version should be possible
  • implement blocking for complex part also OPTIONAL.

In this way, we retain better tuning options for different architectures

Assignee
Assign to
Time tracking