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

Avoid double-counting in Base.summarysize #54555

Closed
wants to merge 1 commit into from

Conversation

xlxs4
Copy link
Contributor

@xlxs4 xlxs4 commented May 22, 2024

Ref #53061

x::Union{Float64, Tuple{Float64, Float64}}
y::Union{Float64, Tuple{Float64, Float64}}
end
let s = S53061[S53061(rand(), (rand(),rand())) for _ in 1:10^5]
Copy link
Member

Choose a reason for hiding this comment

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

not a big deal, but does the array have to be this big to reproduce this?

Copy link
Contributor

Choose a reason for hiding this comment

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

checked, the answer is yes, at least in the current form of the struct, more you reduce the size more you need attempts to find them unequal

Copy link
Contributor

@Tortar Tortar May 22, 2024

Choose a reason for hiding this comment

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

e.g. this needs 10 attempts more or less with 10^4: allequal(Base.summarysize(s) for i in 1:10) # usually false.

Copy link
Member

Choose a reason for hiding this comment

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

why is this nondeterministic? That makes very little sense to me.

Copy link
Contributor

Choose a reason for hiding this comment

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

to me too actually, but I'm not qualified enough to answer :D

Copy link
Member

Choose a reason for hiding this comment

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

It's because the old code has to allocate a box for the value, which it should not have to do, and so the later uniquing by address becomes dependent on GC/allocator behavior. The correct way to fix this is to iterate over the pointers inside a struct instead of over its fields (some fields might be inlined but contain embedded pointers).

@JeffBezanson
Copy link
Member

I believe I have a complete fix in #54606. Thanks for the tests.

@xlxs4 xlxs4 deleted the summarysize-consistency branch May 29, 2024 08:25
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.

4 participants