3D Placement Constraints

[soheilshahrouz]

This PR enhances the supoort for 3D placement constraints to allow the user to specify a layer range for each floorplanning constraint.

Related Issue

Motivation and Context

Each floorplan constraint is limited to a single layer. If the user wants to define a cubic floorplan constraint, she/he has to define multiple rectangular floorplan constraint with the same (x,y) coordinates but for different layers. This PR lets user defne a single floorplan region spanning across multiple layers.

How Has This Been Tested?

Types of changes

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

[vaughnbetz]

The FASM unit test failure seems to be due to a change in the default layers returned for placement constraints on a 2D device:
2024-06-24T20:23:40.5141020Z �[0m�[0;37m/home/runner/work/vtr-verilog-to-routing/vtr-verilog-to-routing/vpr/test/test_vpr_constraints.cpp:51: �[0m�[1;31mFAILED:
2024-06-24T20:23:40.5143053Z �[0m�[0;36m REQUIRE( def_region.get_region_bounds().get_layer_range() == std::make_pair(-1, -1) )
2024-06-24T20:23:40.5144059Z �[0mwith expansion:
2024-06-24T20:23:40.5144514Z �[1;33m {?} == {?}

Updating the REQUIRE to pair(0,0) should work.

@soheilshahrouz also tells me that if we make a custom printer class/method for std::pair catch2 will print objects instead of {?} in the failure.

[vaughnbetz]

Half done ... getting slow.

[vaughnbetz]

Looks good.
Should also add a region constrained case to one of our 3D architecture tests. Small design, A few different kinds of regions (multi-layer, single location, single location with subtile, etc.)