Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
aml
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • argo
  • aml
  • Issues
  • #37

Closed
Open
Opened May 08, 2019 by Swann Perarnau@perarnau
  • Report abuse
  • New issue
Report abuse New issue

Investigate getting rid of static allocation API for building blocks

@videau makes the point that if we really need fast allocations we could implement our own allocators internally. It means we could completely get rid of the DECL, ALLOCSIZE and other macros, and just make the create/destroy client of our own allocators.

That would simplify the code a bit, and the API too. Without allocators, it does cost in performance.

Assignee
Assign to
Second release
Milestone
Second release
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: argo/aml#37