@artmalik: While checking setup violations, I had a path like this with violation.
Path 1: VIOLATED Setup Check with Pin U_FFT2/\dr_reg[13] /CLK
Endpoint: U_FFT2/\dr_reg[13] /SIN (^) checked with leading edge of 'CLK'
Beginpoint: U_BUF2/URAM/\read_addra_reg[1] /Q (v) triggered by leading edge of 'CLK'
I resized the buffers in the path for fixing the violation. When I tried to report the timing result of the path, I got the report like this.
Path 1: VIOLATED Setup Check with Pin U_FFT2/\dr_reg[13] /CLK
Endpoint: U_FFT2/\dr_reg[13] /SIN (^) checked with leading edge of 'CLK'
Beginpoint: U_BUF2/URAM/\read_addra_reg[1] /Q (^) triggered by leading edge of 'CLK'
Why does the edge at the Q pin changes? Also, when I check the timing report, it was seen that the path from Q(^) to SIN(^) contains different instances now!