If you look at the OSVVM *.pro compile scripts you will note there are a number of places where we do not compile certain things – because of a bug in a particular tool.
Note these ports are not OPEN. but instead they have a null range, which is a valid range. Please submit a bug against Xcelium for this issue.
I will make a note to update OSVVM’s scripts not to compile this capability for Cadence at this time. Maybe the solution is to add an additional file that builds this with a small range (0 to 0) for Cadence rather than a NULL range.