/project/mercury2/giant/giant-2025.1.2/user/sramegow/mercury_top_FN.1.2_sta/impl/mercury_top/avo/ECO/ECO012/
├── hm_be_MemCKBFixTransFix.eco
├── hm_clipi_MemCKBFixTransFix.eco
├── hm_clipo_MemCKBFixTransFix.eco
├── hm_dl_MemCKBFixTransFix.eco
├── hm_efr_n_MemCKBFixTransFix.eco
├── hm_efr_s_MemCKBFixTransFix.eco
├── hm_fh_s_MemCKBFixTransFix.eco
├── hm_l1dl_MemCKBFixTransFix.eco
└── hm_l1ul_MemCKBFixTransFix.eco
https://solvnetplus.synopsys.com/apex/pdfViewer?ContentDocumentId=0691U00000886S9QAI
If we dont see RC-008 we are fine as per Synopsys documentation
3.6 Min/Max Bounds Warning (RC-008) Warning: The type of RC delay calculation problems that has just occured prevents the max results from bounding the correct values. (RC-008) In case of one of the previously described failures, a fallback calculation has been selected to guarantee a conservative analysis: C-total is used in max analysis mode and C-zero min analysis mode. However if PrimeTime cannot determine that these fallback values are pessimistic, then it issues an RC-008 message. So this is a supplemental warning that may be due for example to a multi-driven network switching faster than the min delay for this cell or in case of a library extrapolation problem that would return a negative slew. Users should fix the problems associated with the earlier delay calculation warnings, or fix the library or use annotated delay and slew information obtained by circuit simulation