Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

romio,hwloc: fix type errors for x86 #12735

Open
wants to merge 1 commit into
base: v4.1.x
Choose a base branch
from

Conversation

nmorey
Copy link
Contributor

@nmorey nmorey commented Aug 6, 2024

Fix the most egregious type violations that not only prevent with GCC 14 on i586 but that are just bugs too.

Fix the most egregious type violations that not only prevent with GCC 14 on i586
but that are just bugs too.

Signed-off-by: Nicolas Morey <[email protected]>
@github-actions github-actions bot added this to the v4.1.7 milestone Aug 6, 2024
Copy link

github-actions bot commented Aug 6, 2024

Hello! The Git Commit Checker CI bot found a few problems with this PR:

ebf1601: romio,hwloc: fix type errors for x86

  • check_cherry_pick: does not include a cherry pick message (did you need to bot:notacherrypick?)

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

@@ -48,7 +48,7 @@ static bool external_topology = false;

#if HWLOC_API_VERSION >= 0x20000
static size_t shmemsize = 0;
static size_t shmemaddr;
static uintptr_t shmemaddr;
Copy link
Member

Choose a reason for hiding this comment

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

It looks like this value is serialized as a size_t down below. Can you investigate? I don't know where the corresponding deserialization occurs -- you might need to chase that down, too.

I didn't check further to see how the other variables that were converted to uintptr_t are used; those might need to be updated in their usage, too.

Copy link
Member

Choose a reason for hiding this comment

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

@nmorey Any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants