| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This CL also makes input and zeroPoint of dequantizeLinear share
the same OpSupportLimits item, because their limitations are same
for different backends after CL[2] is merged.Does it make sense to have a separate CL for this change? That would make this CL focusing on ORT backend change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This CL also makes input and zeroPoint of dequantizeLinear share
the same OpSupportLimits item, because their limitations are same
for different backends after CL[2] is merged.Does it make sense to have a separate CL for this change? That would make this CL focusing on ORT backend change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This CL also makes input and zeroPoint of dequantizeLinear share
the same OpSupportLimits item, because their limitations are same
for different backends after CL[2] is merged.Wang, Wei4Does it make sense to have a separate CL for this change? That would make this CL focusing on ORT backend change.
sure, I will separate the chages.
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
bool dequantizeLinear_support_int32);```suggestion
bool dequantize_linear_input_support_int32);
```
bool dequantizeLinear_support_int32,```suggestion
bool dequantize_linear_input_support_int32,
```
bool is_default_CPU_EP_first_selected = Environment::IsDefaultCpuEpDevice(```suggestion
bool dequantize_linear_input_support_int32= !Environment::IsDefaultCpuEpDevice(
```
{dequantizeLinear_support_int32 ? kInts4To8Int32
: DataTypeConstraint::kInts4ToInts8,This change seems to be unnecessary.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
{dequantizeLinear_support_int32 ? kInts4To8Int32
: DataTypeConstraint::kInts4ToInts8,This change seems to be unnecessary.
According to WebNN spec, zeroPoint has same "allowed data types" with input, so is it better to keep them same?
{dequantizeLinear_support_int32 ? kInts4To8Int32
: DataTypeConstraint::kInts4ToInts8,Wang, Wei4This change seems to be unnecessary.
According to WebNN spec, zeroPoint has same "allowed data types" with input, so is it better to keep them same?
From the implementation perspective, they can share the same OpSupportLimits item if they are same, just like the changes in CL: https://chromium-review.googlesource.com/c/chromium/src/+/7618977