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

newTimeout is not safe on 32-bit archs #59

Closed
coot opened this issue Jun 1, 2020 · 1 comment · Fixed by #57
Closed

newTimeout is not safe on 32-bit archs #59

coot opened this issue Jun 1, 2020 · 1 comment · Fixed by #57
Labels
bug Something isn't working

Comments

@coot
Copy link
Collaborator

coot commented Jun 1, 2020

As noted by @njd42 :

On a 32 bit machine with a timeout more than ~35min in the future defaultRegisterDelay would be invoked which, in turn, makes use of newTimeout. This calls GHC.registerTimeout where the intrinsic 32 bit constraint rears its ugly head again.

@coot
Copy link
Collaborator Author

coot commented Dec 8, 2022

We haven't fixed newTimeout bug in the pr #57 addresses safety of MonadTimer primitives in the si-timers package.

@coot coot transferred this issue from IntersectMBO/ouroboros-network Dec 9, 2022
@coot coot linked a pull request Dec 9, 2022 that will close this issue
@coot coot closed this as completed in #57 Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant