Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Original Assignee: John Coiner (@jcoiner)
We have an input like this:
always @(posedge clk) begin
Essentially, it's thousands of resettable flops combined into a single always block.
It would be nice if V3Split were smart enough to split this up. There are a few bad consequences of not splitting this up:
What exactly V3Split should output for this case is TBD. We probably don't want to reference the reset signal inline with every assignment (that's more instructions to run, and also more instructions to store.) We might want to break this large always block into a several medium-size always blocks, each of which evaluates the condition once, so that total code size and cpu footprint won't grow much.
Original Redmine Comment
Whoops, here's the above code sample with formatting: