Skip to content

Conversation

@roblatham00
Copy link
Contributor

A partial start at resolving the many places where we potentially store 64 bits worth of data in a 32 bit integer

Man these never go away...

Pull Request Description

Author Checklist

  • Provide Description
    Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
  • Commits Follow Good Practice
    Commits are self-contained and do not do two things at once.
    Commit message is of the form: module: short description
    Commit message explains what's in the commit.
  • Passes All Tests
    Whitespace checker. Warnings test. Additional tests via comments.
  • Contribution Agreement
    For non-Argonne authors, check contribution agreement.
    If necessary, request an explicit comment from your companies PR approval manager.

Copy link
Contributor

@hzhou hzhou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! They looks good overall. A couple place should fixed the type in the struct definitions instead.

@hzhou hzhou changed the title 64-to-32 cleanups bug/warnings: 64-to-32 cleanups Oct 9, 2025
A partial start at resolving the many places where we potentially store
64 bits worth of data in a 32 bit integer
@roblatham00 roblatham00 force-pushed the more-64-to-32-warnings branch from 6bb68f5 to aee88a9 Compare November 10, 2025 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants