Skip to content

math/big: test aliasing of Int.GCD's three results - #81239

Open
a-njli wants to merge 1 commit into
golang:masterfrom
a-njli:bigalias-harness
Open

math/big: test aliasing of Int.GCD's three results#81239
a-njli wants to merge 1 commit into
golang:masterfrom
a-njli:bigalias-harness

Conversation

@a-njli

@a-njli a-njli commented Aug 31, 2026

Copy link
Copy Markdown

checkAliasingTwoResults spells out by hand the ways in which a method's two
results can alias its arguments. That does not extend to GCD, which writes
three results, z, x and y: two of them can alias two different arguments at
the same time, and the combinations are no longer practical to enumerate by
hand.

Add checkAliasingResults, which takes the number of results and tries every
assignment of results to arguments, and register GCD under GCD-ZXY.

The new subtest has teeth. Changing GCD's zero fast path to read b.abs after
z may already have overwritten it, instead of using the lenB snapshot, fails
GCD-ZXY while the existing GCD, GCD-X and GCD-Y subtests all still pass.

checkAliasingTwoResults spells out by hand the ways in which a method's two
results can alias its arguments. That does not extend to GCD, which writes
three results, z, x and y: two of them can alias two different arguments at
the same time, and the combinations are no longer practical to enumerate by
hand.

Add checkAliasingResults, which takes the number of results and tries every
assignment of results to arguments, and register GCD under GCD-ZXY.

The new subtest has teeth. Changing GCD's zero fast path to read b.abs after
z may already have overwritten it, instead of using the lenB snapshot, fails
GCD-ZXY while the existing GCD, GCD-X and GCD-Y subtests all still pass.
@gopherbot

Copy link
Copy Markdown
Contributor

This PR (HEAD: 3b0db6e) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/824585.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

@gopherbot

Copy link
Copy Markdown
Contributor

Message from Gopher Robot:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/824585.
After addressing review feedback, remember to publish your drafts!

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.

2 participants