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
Originally posted by alexmaloteaux April 1, 2023 Hi i already had this issue in the past and each time just updating the package fixed the issue.
However this time i have an issue on github.com/petermattis/goid@latest so i guess i will have to track and use a local "replace" fork.
Could somebody have an idea what exactly this issue is and where to look to fix it ? im facing it with 1.20.2 and it compiles fine without garble.
# github.com/petermattis/goid /tmp/garble-shared1926219085/EBih0wwzivaK/NOrHNRTEp.s:29: expected pseudo-register; found R14 asm: assembly of /tmp/garble-shared1926219085/EBih0wwzivaK/NOrHNRTEp.s failed
The text was updated successfully, but these errors were encountered:
hi , it looks like a tag issue in goid or garble ?, this r14 register is being forced here : https://github.com/petermattis/goid/blob/371a4b8eda085935f3b88517e5cc0daef28dc51b/goid_go1.5_amd64.s#L28 However since go 1.9+ if not wrong only the "slow" version should be used.
Sorry, something went wrong.
@alexmaloteaux I can't reproduce this anymore, can you try if this is fixed for you in master or the latest release? Closing for now.
No branches or pull requests
Discussed in #709
Originally posted by alexmaloteaux April 1, 2023
Hi i already had this issue in the past and each time just updating the package fixed the issue.
However this time i have an issue on github.com/petermattis/goid@latest so i guess i will have to track and use a local "replace" fork.
Could somebody have an idea what exactly this issue is and where to look to fix it ? im facing it with 1.20.2 and it compiles fine without garble.
The text was updated successfully, but these errors were encountered: