ID:332072 Trying to set <First Latency> clock latency that is <Comparison> than previously set <Second Latency> latency. New <First Latency> latency was ignored.

CAUSE: The set_clock_latency command can specify max-rise, max-fall, min-rise, and min-fall delay. One of the minimum delays was larger than its respective maximum delay.

ACTION: Make sure that when the -early option is used with the set_clock_latency command, the delay specified is larger than the delay used with the -late option.