clock setup problems!

Requires setup relationship is 6.666ns, so it's a setup path and optimize hold timing won't help it. The problem is the required longest p2p time is 2.671ns. That usually means you have clock skew on the domain. Break out the path and look at the clcok paths to the source and destination and see why they're different. You're data path is only 3.180ns, so it's fast and easily meets the requirement, it's the clock skew that's hurting you.