Skip to content

Teach alloc-opt to handle atomics a bit better #57208

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

Merged
merged 5 commits into from
Mar 28, 2025
Merged

Conversation

gbaraldi
Copy link
Member

Fixes #57190

The fact that this passes thinks memcpy is a potential issue is quite annoying so it deserves a decent refactor, which flows through the type information from julia instead of trying to regenerate it on site, specially given that opaque pointers means we can't really instrospect into pointers at all

@gbaraldi gbaraldi requested a review from vtjnash January 30, 2025 21:21
@KristofferC KristofferC added the backport 1.12 Change should be backported to release-1.12 label Feb 11, 2025
This was referenced Feb 14, 2025
@oscardssmith
Copy link
Member

How does this interact with #57010?

@gbaraldi
Copy link
Member Author

It doesn't really

@KristofferC KristofferC mentioned this pull request Mar 24, 2025
27 tasks
@vtjnash vtjnash merged commit 2c7527b into master Mar 28, 2025
5 of 7 checks passed
@vtjnash vtjnash deleted the gb/alloc-opt-atomics branch March 28, 2025 14:36
KristofferC pushed a commit that referenced this pull request Mar 31, 2025
Fixes #57190

The fact that this passes thinks memcpy is a potential issue is quite
annoying so it deserves a decent refactor, which flows through the type
information from julia instead of trying to regenerate it on site,
specially given that opaque pointers means we can't really instrospect
into pointers at all

(cherry picked from commit 2c7527b)
@KristofferC KristofferC mentioned this pull request Mar 31, 2025
36 tasks
KristofferC pushed a commit that referenced this pull request Mar 31, 2025
Fixes #57190

The fact that this passes thinks memcpy is a potential issue is quite
annoying so it deserves a decent refactor, which flows through the type
information from julia instead of trying to regenerate it on site,
specially given that opaque pointers means we can't really instrospect
into pointers at all

(cherry picked from commit 2c7527b)
@KristofferC KristofferC mentioned this pull request Apr 4, 2025
51 tasks
@KristofferC KristofferC removed the backport 1.12 Change should be backported to release-1.12 label Apr 9, 2025
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.

Segfault from @atomic operation on typed field (miscompilation?)
5 participants