Tighten the clock period for gt2n designs

[maliberty]

Produce negative slacks

[gemini-code-assist]

Code Review

This pull request reduces the clock period (clk_period) in the SDC constraint files for the aes, gcd, and jpeg designs under the gt2n flow. However, the changes also removed helpful explanatory comments regarding the non-standard time unit (time_unit = 1 ps) and target frequencies. The reviewer recommends retaining and updating these comments to maintain readability and prevent confusion, as SDC files typically default to nanoseconds.

[openroad-ci]

🔍 QoR check

Metrics reflect the PR merge build — i.e. what will land on the target branch.

Commit 512b8b0 · Jenkins build #1 · Baseline: build · View build on dashboard

62 design(s) checked — 2 with regression(s), 0 without a comparable baseline.

❌ gt2n/gcd base — 7 failing metric(s)

Metric	target	base	delta	limit	band
cts__timing__setup__tns	-786.696	0	—	-100.0	PeriodPadding 20%
cts__timing__setup__ws	-62.9036	158.356	-139.72290282654274%	-25.0	PeriodPadding 5%
finish__timing__setup__tns	-1187.76	0	—	-100.0	PeriodPadding 20%
finish__timing__setup__ws	-68.8317	150.061	-145.86914654707087%	-25.0	PeriodPadding 5%
globalroute__timing__setup__tns	-1187.75	0	—	-100.0	PeriodPadding 20%
globalroute__timing__setup__ws	-68.8299	150.061	-145.8679470348725%	-25.0	PeriodPadding 5%
placeopt__design__instance__area	21.5127	18.5432	16.013956598645326%	21.32468	Padding 15%

❌ gt2n/jpeg base — 4 failing metric(s)

Metric	target	base	delta	limit	band
cts__timing__setup__tns	-15681.9	0	—	-200.0	PeriodPadding 20%
cts__timing__setup__ws	-60.0663	131.953	-145.52098095534015%	-50.0	PeriodPadding 5%
finish__timing__setup__tns	-4650.05	0	—	-200.0	PeriodPadding 20%
globalroute__timing__setup__tns	-4617.66	0	—	-200.0	PeriodPadding 20%