ppc32 and logtest repairs#1045
Merged
Merged
Conversation
mflatt
force-pushed
the
ppc32-atomic-alloc
branch
from
35acf23 to
22a7c41
Compare
Contributor
|
Thanks for finding and fixing this! Please update the release notes. |
burgerrg
approved these changes
May 11, 2026
ober
pushed a commit
to ober/ChezScheme
that referenced
this pull request
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repairs two problems related to #1043.
One problem is specific to ppc32 and
__atomic __alloc.The other one affects
logteston all platforms when given a mixture of fixnum and bignum arguments. That kind of mixture is probably more likely on a 32-bit platform, so that may be why testing did not discover the problem before, but it's not clear why ppc32 was affected more than other 32-bit platforms.