Skip to content
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

config checker being overzealous on bitwidth? #11

Open
jvoigtlaender opened this issue Dec 9, 2024 · 0 comments
Open

config checker being overzealous on bitwidth? #11

jvoigtlaender opened this issue Dec 9, 2024 · 0 comments

Comments

@jvoigtlaender
Copy link
Member

I suspect that in

| maximum ([ flows + snd derivedFlowsNew | uncurry (/=) derivedFlowsNew ]
++ [ snd derivedFlowsReused | derivedFlowsReused /= (0, flows) ]
++ [ b | (a,b) <- [ startNodes
, shallowHistoryNodes
, deepHistoryNodes
, triggerNames
, forkNodes
, joinNodes
, totalNodes ]
, 0 < a && a /= b ])
> 2 ^ (bitwidth - 1) - 1
some or even all uses of the second pair component could be replaced by the first pair component (thus triggering that config error less often).

@jvoigtlaender jvoigtlaender changed the title config checker overzealouz on bitwidth? config checker being overzealous on bitwidth? Dec 9, 2024
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

No branches or pull requests

1 participant