Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Merge requests
  • !76

Merged
Created Feb 11, 2021 by Glenn K. Lockwood@glockDeveloper

change all memory size variables to long ints

  • Overview 1
  • Commits 1
  • Changes 3

Darshan uses a couple of variables to track module memory footprints that involve int instead of long (or preferably size_t). I changed these to type long to harmonize with the existing static long darshan_mod_mem_quota in this MR, but should these all more properly be size_t? If so I can change.

The problem that triggered this was trying to build with --with-mod-mem=2048; GCC detected a possible overflow condition.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/BIGmodules