-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: GOSSAFUNC=main open ssa.html: permission denied #33278
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
Comments
It seems to me that this is because |
Can confirm this suspicion. Making
However, I guess this is not what I was hoping for - I just want to have Weirdly enough, now I have the following situation:
so no complaints (although the runtime-directory is not writeable by this user anymore). But there are no Also. executing with
UPDATE: it seems to "randomly" write the |
Yes, this is a common stumbling block. If your code hasn't changed, it will not regenerate the ssa.html file. Either change the code, or rename your function to something else. If your function is main, you need to change the code unfortunately. Btw, you can work around the issue if you just use |
Ah yes. Changed a line in the code and the Definitely a stumbling block. Thanks for the tip with |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
It does with both versions reported above.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I saw this blogpost and wanted to try out the SSA HTML thing. I thus wrote the
main.go
file and ran the command:NOTE: as i have go modules enabled, I also ran
go mod init ssatest
.the permissions in the directory are rwx for all users.
a normal build with
go build .
, orgo build main.go
works fine.And just for demonstration; when changing the file to this:
main.go
so it seems to only occur when using
GOSSAFUNC=main
.For the sake of completion:
output with
GOSSAFUNC=main+
I'm a complete newbie in this topic, so maybe it's just me doing something wrong 🙂
The text was updated successfully, but these errors were encountered: