cmd/compile: add the concept of dual instructions to ssa/_gen
commutative ops were renamed triviallyCommutative.
And I've added a dual field to opInfo, which defaults 0 for
non commutative ops, and self for triviallyCommutative ones.
Due to the diff being huge dual instructions are completely
useless for now, as this means this diff is only the field
rename and gen changes.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Will try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Will try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
I am not expecting this to get in before the freeze. Don't worry about being timely.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
JorropoWill try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
I am not expecting this to get in before the freeze. Don't worry about being timely.
If conflicts are too bad I can keep the `commutative` name but I think `triviallyCommutative` is better.
JorropoWill try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
JorropoI am not expecting this to get in before the freeze. Don't worry about being timely.
If conflicts are too bad I can keep the `commutative` name but I think `triviallyCommutative` is better.
I'd really rather leave `commutative` as it is currently named and have another name for this new thing. It is kind of anticommutative, but not quite. dualCommutative or skewCommutative?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
JorropoWill try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
JorropoI am not expecting this to get in before the freeze. Don't worry about being timely.
Keith RandallIf conflicts are too bad I can keep the `commutative` name but I think `triviallyCommutative` is better.
I'd really rather leave `commutative` as it is currently named and have another name for this new thing. It is kind of anticommutative, but not quite. dualCommutative or skewCommutative?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
JorropoWill try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
JorropoI am not expecting this to get in before the freeze. Don't worry about being timely.
Keith RandallIf conflicts are too bad I can keep the `commutative` name but I think `triviallyCommutative` is better.
JorropoI'd really rather leave `commutative` as it is currently named and have another name for this new thing. It is kind of anticommutative, but not quite. dualCommutative or skewCommutative?
`commuted` ?
`asm: "CMOVQEQ", commuted: "CMOVQNE"`
Sure, an optional `commuted` or `commutedOp` field would be fine.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
JorropoWill try to get this reviewed in a timely way, there's loads of conflicts with machine-generated code from SIMD right now. In theory a trivial update to the generators, in practice we're already stepping on each other's toes trying to land SIMD work.
JorropoI am not expecting this to get in before the freeze. Don't worry about being timely.
Keith RandallIf conflicts are too bad I can keep the `commutative` name but I think `triviallyCommutative` is better.
JorropoI'd really rather leave `commutative` as it is currently named and have another name for this new thing. It is kind of anticommutative, but not quite. dualCommutative or skewCommutative?
Keith Randall`commuted` ?
`asm: "CMOVQEQ", commuted: "CMOVQNE"`
Sure, an optional `commuted` or `commutedOp` field would be fine.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |