We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Use simple analysis to eliminate duplicate instrumentation in cases like: x = ...; ... = x; Currently it leads to insertion of 2 raceread() calls.
The text was updated successfully, but these errors were encountered:
Comment 1:
Labels changed: added repo-main.
Sorry, something went wrong.
Comment 2:
Adding Release=None to all Priority=Someday bugs.
Labels changed: added release-none.
Currently it leads to insertion of 2 raceread() calls.
Is this report actually about duplicate raceread calls, or is it about redundant racewrite+raceread calls?
raceread
racewrite
If I compile the code below with -S -race, I see one racewrite call for the x = y assignment, and then one raceread call for the return x statement.
-S -race
x = y
return x
package p var x int func f(y int) int { x = y return x }
No branches or pull requests
The text was updated successfully, but these errors were encountered: