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
cmd/compile: should use FNEG for float32/64 on ppc64 #9598
Labels
Milestone
Comments
minux
changed the title
cmd/9g: should use AFNEG for float64
cmd/9g: should use FNEG for float64
Jan 15, 2015
minux
changed the title
cmd/9g: should use FNEG for float64
cmd/9g: should use FNEG for float32/64
Jan 15, 2015
I believe this is too unimportant for right now. Finishing the port (especially those nagging cgo details) takes priority over microoptimizations. Removing milestone. |
rsc
changed the title
cmd/9g: should use FNEG for float32/64
cmd/compile: should use FNEG for float32/64 on ppc64
Jun 8, 2015
@dr2chase does ppc64 SSA do this? Can we close this issue? |
It should be fixed in 1.8:
|
Thanks. Closing. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It always generates FMUL -1 for OMINUS now.
However, Power does support double precision FNEG, it just
doesn't support single precision FNEGS.
But it's still fine to use FNEG for both float32 and float64, as
Power ISA documents that FNEG simply inverts bit 0.
The text was updated successfully, but these errors were encountered: