Skip to content

[AIESW-23180] Duplicate onnx.DequantizeLinear if it has multiple consumers while removing binary op#527

Open
tanzeel-amd wants to merge 2 commits into
Xilinx:feature/onnx-to-tosafrom
tanzeel-amd:patch-2
Open

[AIESW-23180] Duplicate onnx.DequantizeLinear if it has multiple consumers while removing binary op#527
tanzeel-amd wants to merge 2 commits into
Xilinx:feature/onnx-to-tosafrom
tanzeel-amd:patch-2

Conversation

@tanzeel-amd
Copy link
Copy Markdown

Issue: When a dequantize node feeds multiple operations (e.g., Sigmoid and Mul), folding a binary operation into it updated the scale for all users, causing incorrect results.

Fix: Detect when a dequantize node has multiple users and duplicate it before updating the scale, so only the binary operation path uses the new scale while other users remain unchanged.

Impact: Ensures correctness when optimizing quantized models with shared dequantize nodes, preventing incorrect quantization scale propagation.

…ore updating the scale, so only the binary operation path uses the new scale while other users remain unchanged
@tanzeel-amd tanzeel-amd changed the title Duplicate onnx.DequantizeLinear if it has multiple cinsumers while removing binary op [AIESW-23180] Duplicate onnx.DequantizeLinear if it has multiple cinsumers while removing binary op Jan 23, 2026
@tanzeel-amd tanzeel-amd changed the title [AIESW-23180] Duplicate onnx.DequantizeLinear if it has multiple cinsumers while removing binary op [AIESW-23180] Duplicate onnx.DequantizeLinear if it has multiple consumers while removing binary op Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant