I have noticed that my design is unroutable when I tell PAR to ignore my timing constraints (-x), but it runs okay if I do not. Wouldn't it normally be more difficult to both satisfy timing constraints and route a design, than to just route it?
This option is referred to as Performance Evaluation Mode and involves the automatic constraint of all clocks. Several cases have been seen where this automatic constraining process over-constrains the design, which can lead to routing failures.
If the goal is to disable timing driven operation entirely, the hidden PAR switch "-ntd" can be used instead.
This problem has been fixed in the latest 8.2i Service Pack available at:
The first service pack containing the fix is 8.2i Service Pack 1.