How to apply time constraints to counter?

okay. if counter consist only one part so you don't need any special time constraints. -< Okay

if you counter consist of two (for one direction) or three (for both direction) parts you can apply multicycle constraints to middle part to relax Fitter efforts.

So if I create first( and last) part as only 1bit, i'll apply multicycle setup=2 and hold=1 to another(middle) part? <- Yes or No?

I asked cause I see difference for Fmax in TimeQuest reports.

Actually I create more than one counter and for each i must apply its own constraints. but as functional it looks like only one.

You have only one(two) part(s) small in size that runs every cycle, the reminder can be great as long as your satisfied with TimeQuest results.

Will it bring any problems if big part runs on the same clock as small but with clock-enable or even with sync_load?