I/O Timing constraints

I am not concerned about timings of these slow signals, I am actually trying to create more space for others :) I want to ease routing efforts by giving Quartus an imaginary, slow (57.6K) clock, so that faster signals could be routed easily.

--- Quote Start ---

Then you can ignore their timing by setting them to false paths or specifying multicycles.

--- Quote End ---

Actually, Multicycle soulds resonable, but I ve never seen like multicycle_path with quite large numbers like 1700 :confused::

set_multicycle_path -setup -end -from  -to  1736

false_path seems a bit risky, it may give different results compile to compile? false_path == completly ignore timings?

By the way, thank you for quick reply.