Skip to content

[ODIN] ifdef-endif not recognized properly #1770

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

Closed
ArashAhmadian opened this issue Jun 9, 2021 · 2 comments
Closed

[ODIN] ifdef-endif not recognized properly #1770

ArashAhmadian opened this issue Jun 9, 2021 · 2 comments
Labels

Comments

@ArashAhmadian
Copy link
Contributor

ifdef-endif seems to not be recongized properly by Odin. The adder circuits located here are syntactically correct however Odin marks the output sum as undriven.

Expected Behaviour

Should synthesize without getting rid of the output sum as it is driven.

Current Behaviour

The output is thought to be undriven and is removed:

home/ahmadi55/vtr-verilog-to-routing/vtr_flow/benchmarks/arithmetic/generated_circuits/adder_trees/verilog/test.v:13:3: 
warning[NETLIST]:  This output is undriven (adder_tree_top^sum~0) and will be removed
    11 | input clk;
    12 | input [`ADDER_WIDTH+0-1:0] isum0_0_0_0, isum0_0_0_1, isum0_0_1_0, isum0_0_1_1, isum0_1_0_0, isum0_1_0_1, isum0_1_1_0, isum0_1_1_1;
    13 | output [`ADDER_WIDTH  :0] sum;
          ^~~~
    14 | reg    [`ADDER_WIDTH  :0] sum;
    15 |

If the ifdef-endif strucutres are simply removed and the non-blocking statement sum<=sum0 or sum <= sum0_0 are put in the always block, the circuit synthesizes fine.

Steps to Reproduce

  1. Attempt to synthesize a circuit under: https://github.com/verilog-to-routing/vtr-verilog-to-routing/tree/master/vtr_flow/benchmarks/arithmetic/generated_circuits/adder_trees/verilog.
    (e.g. Run ./odin_II -V ../vtr_flow/benchmarks/arithmetic/generated_circuits/adder_trees/verilog/adder_tree_2L_004bits.v from the ODIN_II directory)
ArashAhmadian added a commit to ArashAhmadian/vtr-verilog-to-routing that referenced this issue Jun 9, 2021
Copy link

github-actions bot commented May 9, 2025

This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.

@github-actions github-actions bot added the Stale label May 9, 2025
Copy link

This issue has been marked stale for 15 days and has been automatically closed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant