Hi Matthias and Jakob, this fixed a newly reported bug by CL: https://chromium-review.googlesource.com/c/v8/v8/+/7299683 . PTAL, Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (offset0 != offset1) {Is it expected that we never use `offset1` here?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (offset0 != offset1) {Is it expected that we never use `offset1` here?
I think offset1 is already reduced here and maybe used by other nodes. Here we emit offset0 just to make it valid when emit the Simd256LoadTransform node.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (offset0 != offset1) {Chen, YolandaIs it expected that we never use `offset1` here?
I think offset1 is already reduced here and maybe used by other nodes. Here we emit offset0 just to make it valid when emit the Simd256LoadTransform node.
We can also skip this check, just it will generate a duplicate offset constant.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
if (offset0 != offset1) {Chen, YolandaIs it expected that we never use `offset1` here?
Chen, YolandaI think offset1 is already reduced here and maybe used by other nodes. Here we emit offset0 just to make it valid when emit the Simd256LoadTransform node.
We can also skip this check, just it will generate a duplicate offset constant.
Ah, makes sense, fine for me to skip the duplication here, though GVN should handle this as well.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (offset0 != offset1) {Chen, YolandaIs it expected that we never use `offset1` here?
Chen, YolandaI think offset1 is already reduced here and maybe used by other nodes. Here we emit offset0 just to make it valid when emit the Simd256LoadTransform node.
Matthias LiedtkeWe can also skip this check, just it will generate a duplicate offset constant.
Ah, makes sense, fine for me to skip the duplication here, though GVN should handle this as well.
I think this condition is always true: `offset0` comes from the `__ input_graph()`, `offset1` comes from the `__ output_graph()`, so they can't ever be the same node. So unless I'm missing something, I think the change in this file is actually a no-op? If so, it'd be simpler to revert it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
if (offset0 != offset1) {Chen, YolandaIs it expected that we never use `offset1` here?
Chen, YolandaI think offset1 is already reduced here and maybe used by other nodes. Here we emit offset0 just to make it valid when emit the Simd256LoadTransform node.
Matthias LiedtkeWe can also skip this check, just it will generate a duplicate offset constant.
Jakob KummerowAh, makes sense, fine for me to skip the duplication here, though GVN should handle this as well.
I think this condition is always true: `offset0` comes from the `__ input_graph()`, `offset1` comes from the `__ output_graph()`, so they can't ever be the same node. So unless I'm missing something, I think the change in this file is actually a no-op? If so, it'd be simpler to revert it.
Never mind, I was confused.
| 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. |
[wasm][revec] Avoid changing default node group
Changing default node group caused missing node mapping. Instead we can
check the offsets for duplicate LoadSplat when reduce the nodes.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |