Timequest Report Datasheet (setup time and hold time)

Just an additional viewpoint, but I'm not a big fan of the Report Datasheet(but understand why it's easy to look at.)

First, it's not an actual constraint. So if anything changes and you have to recompile, those values might change. If you constrain your I/O, then use those constraints as the datasheet, and as long as it meets timing, you know you've met those constraints.

Secondly, it uses Tsu/Th/Tco/Min Tco. These are easy to understand, and work most of the time, but have issues when you a) use the falling edge of the clock or b) phase-shift the clock. For example, if you have a Tco of 8ns, and one day change the code so it is clocked on the falling edge(and let's say it's a 6ns clock), does your Tco become 2ns, 14ns, or stay at 8ns? It really depends. Phase-shifting the clock has similar implications. I know most I/O cases don't have either of these, or users know how to incorporate them, but just something to be aware of.

(I don't like it, but I've used Report Datasheet to get a "quick feel" on where my I/O timing is, and appreciate it's readability...)