fixes #18238; Nested object construction can zero same memory multiple times for --mm:refc#25834
Conversation
--mm:refc
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the C backend’s object-construction codegen (genObjConstr) to reduce redundant zero-initialization during nested object construction, targeting the --mm:refc case described in issue #18238.
Changes:
- Refines the
needsZeroMemcondition incompiler/ccgexprs.nimto avoid unconditional zeroing based solely on the selected GC, and instead incorporatecontainsGarbageCollectedRef(t)plus theoptSeqDestructorssetting.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
fixes #18238
This pull request makes a targeted change to the object construction logic in the
genObjConstrprocedure. The main update refines the conditions under which memory zeroing is required during object construction, making the behavior more accurate for different garbage collection and destructor options.Key logic update:
needsZeroMemcondition ingenObjConstrto check for the presence of garbage-collected references and theoptSeqDestructorsoption, instead of relying solely on the selected garbage collector and field flags. This ensures memory is zeroed only when necessary, potentially improving performance and correctness.The original test case has already been fixed for
ORC, now extends it torefc: if a constructor is fully initialized, it does not need a zero-fill step