[WARNING IFP-0028] Core area lower left (1.000, 1.000) snapped to (1.026, 1.080)

[oharboe]

Description

I get this warning with CORE_UTILIZATION, unexpected.

The current output is a presumably something that accrued over time and not a single consistent overall report:

number instances in verilog is 2048974
[WARNING IFP-0028] Core area lower left (1.000, 1.000) snapped to (1.026, 1.080).
[INFO IFP-0001] Added 1685 rows of 16858 site asap7sc7p5t.

Suggested Solution

Change warning to something less omnious than a warning and useful(fast, early accurate information is helpful) and create a single consistent format instead of having various modules contribute to this information in their own format:

Instances: ...
Die area: ...
Core area: ...
Snapped to grid: yes/no

Additional Context

No response

[maliberty]

This seems to be two unrelated requests.

The warning just says that you gave a location that is not a multiple of a placement site so we snapped it to one. As we are changing user input it seems a bit more than just an info. Would mentioning the site grid make it clearer. I presume the value came from CORE_MARGIN.

The message is quite dated and I would consider just removing it as we report in the metrics.

[oharboe]

Ok. I will leave you to it to scrub/combine/clean up.

Early readable consistent actionable feedback to adjust floorplan is the use case I am thinking of here.

[gadfort]

@maliberty While the message could probably benefit from improvements, I think it is helpful for users to be notified in the log (that's where I'm going to look for why the core area does not match what I requested). Vote to keep it.

[maliberty]

Ok, do we just want:

Instances: ...
Die area: ...
Core area: ...

[oharboe]

👍 Is there any other useful actionable information at this point?

[rovinski]

I vote to keep the warning too for the same reason. Proprietary tools also mark this as a warning. The only difference is that I might explicitly add that the reason for snapping is due to the site size.