Flow stuck at "Global resizer timing optimization" for many hours now. Previously it used to be stuck at "PL Resizer timing optimization", but setting "PL_RESIZER_ALLOW_SETUP_VIOS" solved that. But setting "GLB_RESIZER_ALLOW_SETUP_VIOS" doesn't help. Also the timing analysis step before "Global resizer timing optimization" doesn't show any setup violations. Any help is appreciated !

[INFO GRT-0002] Maximum degree: 2
[INFO GRT-0001] Minimum degree: 2
[INFO GRT-0002] Maximum degree: 2

seems flow is running. Based on complexity & system resource this stage will take more time. It is good to fix PL Resizer timing optimization issue, to avoid issue during routing.

@Vijayan Krishnan In PL timing optimization my 16GB RAM eventually fills up and gets killed. I think it will be the same for gl timing optimization as well. So I don't have much choice. Is there anything else I can do?

Increase the RAM and try. Otherwise harden as small macros and integrate it.

@Vijayan Krishnan If possible can you provide me a sample config file for including hardened macros? Can I just reuse the user_project_wrapper config and edit it?

Yes you can use

Oh thank you, In the proj_wrapper config, pl/glb timing optimizations are turned off, is there an issue with turning them on?

It's depends upon how you are doing integration. Only macros connection and no functions or no std cell placed mean keep those off. If any new connections with std cell mean you should turn on those.

But even when we are just connecting macros, there could be hold violations arising in the input ports right? So wouldn't it be better to keep those settings on so that they can be corrected?

Only if I see the RTL and report able to comment on this