Timequest reports setup violation in clock "n/a"

It ignores the manual phase-shift in it's analysis, but if you tweak the constraint in the opposite direction, it all works out. (I hate to say ignores, since that sounds like a mistake. Phase-shifts affect your edges, which affect the setup and hold relationships. set_max/min_delay is purposely meant to override the default setup and hold relationships, i.e. let the user tweak it to whatever they want, and as such, the original phase-shift is not used in the new calculation). So you can tweak your settings in the opposite direction, or learn how the set_input/output_delay constraints work. I posted a TimeQuest .ppt in here that talks about default setup and hold relationships, multicycles, etc. It's probably worth looking at that before proceeding. (It doesn't cover the I/O constraints, but it still might be worth looking at to understand setup and hold relationships.)