False paths and max delay
You will learn
What a false path declares, what a max delay bounds instead, and what removing a check looks like in a repository.
set_false_path tells the analyzer a crossing is asynchronous: stop reporting it, the synchronizer owns it. Used beyond that, it silences real failures, so a CDC flow pairs it with set_max_delay, which bounds a synchronizer path instead of ignoring it -- the two or three flops must still be close in time. A false path is a check deliberately removed, and the widget shows what removing checks looks like in a repository: 14 days of merged pull requests, which added tests, changed them or removed asserts, with the exact lines from git. The spec frame opens timing.t27, the analysis the exceptions carve holes in.