Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
panloader
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • Panfrost
  • panloader
  • Issues
  • #1

Closed
Open
Opened Mar 23, 2018 by Alyssa Rosenzweig@alyssa💜Owner

Determining IS_64_SEPERATE_SYMBOL

For context, open/open64 as well as mmap/mmap64 are sometimes seperate pairs of functions but sometimes are just aliased with the preprocessor. A given build of panwrap needs to know this correctly, or otherwise it will either:

  • Not compile at all, due to duplicate symbols
  • Compile but not trace anything, since it binds the wrong function

The current test in meson is broken. At some point (i.e. before Bifrost), this will need to be fixed.

I suspect a simple check for a 64-bit host may be enough, at least for glibc builds. No idea what bionic does at this point.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: panfrost/panloader#1