Upload 173 files

Bug/3217.md

@@ -0,0 +1,25 @@
+# DRC error in detailed routing - Short
+
+Tool: Detailed Routing
+
+Subcategory: Routing violation
+
+## Conversation
+
+### oharboe
+What is detailed routing trying to do here? The grey area is a macro.
+
+Is the detailed route simply spilling onto the macro because it can't find a valid place to put the wire?
+
+![image](https://user-images.githubusercontent.com/2798822/233313803-be73a31c-255b-4857-acb3-d304cb37db11.png)
+
+
+![image](https://user-images.githubusercontent.com/2798822/233314427-9f2f4378-db70-4f2f-bc54-c23118c5e2b9.png)
+
+
+### oharboe
+Since no-one answers, I'm thinking I guessed right :-)
+
+### maliberty
+Most likely (assuming the layers are blocked and this isn't just available resource).
+

Bug/3314.md

@@ -0,0 +1,138 @@
+# [WARNING STA-0139] ... 63.3687 is not a float.
+
+Tool: OpenSTA
+
+Subcategory: Locale issue
+
+## Conversation
+
+### oharboe
+I get a lot of these warnings when I run `make gui_final`
+
+This is with the latest ORFS.
+
+What are they?
+
+```
+$ make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk place
+```
+
+
+```
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 63.3687 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 79.0805 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 106.935 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 156.622 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 248.596 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 397, 432.982 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 0.36 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 0.72 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 1.44 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 2.88 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 5.76 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 11.52 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 406, 23.04 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 415, 12.8576 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 415, 15.7364 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 415, 21.3969 is not a float.
+[WARNING STA-0139] /home/oyvind/OpenROAD-flow-scripts/flow/platforms/asap7/lib/asap7sc7p5t_AO_RVT_TT_nldm_211120.lib.gz line 415, 32.5931 is not a float.
+```
+
+### vijayank88
+@oharboe 
+I ran with latest commit and not able to get similar logs.
+
+### maliberty
+The report says 'make place' and 'make gui_final' which are not a compatible pair.   I can't reproduce this either even running all the way through.
+
+### oharboe
+```
+rm -rf results/
+make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk place
+make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk gui_place
+```
+
+```
+$ make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk gui_place
+[INFO][FLOW] Using platform directory ./platforms/asap7
+[INFO-FLOW] ASU ASAP7 - version 2
+Default PVT selection: BC
+ODB_FILE=./results/asap7/mock-array-big_Element/base/3_place.odb /home/oyvind/OpenROAD-flow-scripts/tools/install/OpenROAD/bin/openroad -gui  ./scripts/gui.tcl
+Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
+This plugin does not support propagateSizeHints()
+OpenROAD v2.0-8114-gaa1f8060d 
+This program is licensed under the BSD-3 license. See the LICENSE file for details.
+Components of this program may be licensed under more restrictive licenses which must be honored.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 0.72 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 1.44 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 2.88 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 5.76 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 11.52 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 23.04 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 46.08 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 0.72 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 1.44 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 2.88 is not a float.
+[WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 5.76 is not a float.
+```
+
+
+### oharboe
+@maliberty Aha! This is a locale issue. In their wisdom a hundred years ago, Norwegians decided to use "," to separate integers from fractions in floating point... So "12.34" is not a valid float in Norwegian locale, rather "12,34" is.
+
+The evidence that this is the problem is that setting `LC_NUMERIC="en_GB.UTF-8"` fixes the problem.
+
+In this case, the locale is decided by the format that is being parsed, it is not a human readable/writeable number.
+
+Let's see if this works: https://github.com/Pinata-Consulting/OpenSTA/tree/lock-down-strtof-locale
+
+Yep :-)
+
+This also explains why we don't see this when we run from docker, only local install.
+
+### maliberty
+Brazil has the same issue.  https://github.com/The-OpenROAD-Project/OpenROAD/blob/6920ac530b6959f742e75b7f55062b1642730b14/src/Main.cc#L217  attempts to solve this.  Do none of the locales exist on your systems?
+
+### maliberty
+Would you try your strtof check along with getlocale after these various points to try to see what's going on.  I think this works in Brazil so I'm trying to understand what's different here.  @luis201420 any insights?
+
+
+### maliberty
+Perhaps it relates to LC_NUMERIC or another.  Can you try unsetting all LC_* but LC_ALL in your environment to see if that matters?
+
+### oharboe
+@maliberty @luis201420 With this change, I no longer get the warnings.
+
+This is just a quick hack, I think it would be better if someone who knows what is going on and are aware of other edgecases articulates the pull request :-)
+
+```
+diff --git a/src/gui/src/gui.cpp b/src/gui/src/gui.cpp
+index 355aa6842..7d79d99a3 100644
+--- a/src/gui/src/gui.cpp
++++ b/src/gui/src/gui.cpp
+@@ -1141,6 +1141,16 @@ int startGui(int& argc,
+   }
+   main_window->show();
+ 
++  // This avoids problems with locale setting dependent
++  // C functions like strtod (e.g. 0.5 vs 0,5).
++  std::array locales = {"en_US.UTF-8", "C.UTF-8", "C"};
++  for (auto locale : locales) {
++    if (std::setlocale(LC_ALL, locale) != nullptr) {
++      break;
++    }
++  }
++
++
+   gui->setLogger(open_road->getLogger());
+ 
+   main_window->setDatabase(open_road->getDb());
+```
+
+
+### maliberty
+@luis201420 will you look at this since you can reproduce it
+
+### oharboe
+I guess this has been identified as a bug in OpenROAD, given that there are frameworks that set the locale after OpenROAD has set the locale.
+

Bug/3362.md

@@ -0,0 +1,60 @@
+# Where does "Error: tdms_place.tcl, 35 cannot create std::vector larger than max_size()"
+
+Tool: Global Placement
+
+Subcategory: Memory allocation error
+
+## Conversation
+
+### oharboe
+I want to debug it, but I searched the code and couldn't find this error message in the source.
+
+```
+[INFO GPL-0003] SiteSize: 54 270
+[INFO GPL-0004] CoreAreaLxLy: 2160 2160
+[INFO GPL-0005] CoreAreaUxUy: 25922160 25922160
+Error: tdms_place.tcl, 35 cannot create std::vector larger than max_size()
+Command exited with non-zero status 1
+```
+
+
+### maliberty
+My guess is this is an STL exception and not in the OR code.  In gdb try 'catch throw' to see when it is being thrown.
+
+### oharboe
+This is odd... 48000*96000 = 4608000000. Ah. overflow.
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/ca384a53-04da-42fd-9039-014b3bdd89f9)
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/a0156546-48aa-4c6c-84a1-ee9b89647226)
+
+
+```
+D$ git diff
+diff --git a/src/gpl/src/placerBase.cpp b/src/gpl/src/placerBase.cpp
+index 30ff82771..4f2c10b4e 100644
+--- a/src/gpl/src/placerBase.cpp
++++ b/src/gpl/src/placerBase.cpp
+@@ -1002,8 +1002,8 @@ void PlacerBase::initInstsForUnusableSites()
+ {
+   dbSet<dbRow> rows = db_->getChip()->getBlock()->getRows();
+ 
+-  int siteCountX = (die_.coreUx() - die_.coreLx()) / siteSizeX_;
+-  int siteCountY = (die_.coreUy() - die_.coreLy()) / siteSizeY_;
++  long siteCountX = (die_.coreUx() - die_.coreLx()) / siteSizeX_;
++  long siteCountY = (die_.coreUy() - die_.coreLy()) / siteSizeY_;
+ 
+   enum PlaceInfo
+   {
+```
+
+gives me:
+
+```
+[INFO GPL-0002] DBU: 1000
+[INFO GPL-0003] SiteSize: 54 270
+[INFO GPL-0004] CoreAreaLxLy: 2160 2160
+[INFO GPL-0005] CoreAreaUxUy: 25922160 25922160
+Error: out of memory.
+```
+

Bug/3589.md

@@ -0,0 +1,26 @@
+# how to fix metal spacing DRCs
+
+Tool: Detailed Routing
+
+Subcategory: DRC violation
+
+## Conversation
+
+### gkamendje
+After 64 iterations DRT stopped on my design a generated a DRC report. It turns out that most of the DRC are related to METAL1 spacing  (with net VSS) and Metal SpacingTableTw. The design is not very congested so I wonder why the tool could not fix these rules. Could it be that I am missing something here (maybe something in my platform definition)? Is there a way to fix these violations? 
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/56942214/af73acfe-92fb-4590-baaf-31be8548e95e)
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/56942214/4ed7f795-fef7-4d49-9f78-76b85c9cae37)
+
+
+
+### maliberty
+Can you provide a test case?  
+
+### maliberty
+You have very wide METAL1 power stripes:
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/761514/ec146977-bcb3-4725-8140-4bef3c0137ef)
+
+The pin is less than the min space (0.19 < 0.23) from the stripe so there is always going to be a DRC error here.   You need to adjust your PDN definition to be resolve this.
+

Bug/3597.md

@@ -0,0 +1,53 @@
+# Detailed routing loops instead of straight wire...
+
+Tool: Detailed Routing
+
+Subcategory: Routing pattern anomaly
+
+## Conversation
+
+### oharboe
+I've been fixing some problems in mock-array in positioning of macros and pins not being aligned and now things are working well.
+
+However, I found this curious thing when inspecting, a detailed routing loop :-)
+
+I don't see any reason why a horizontal wire wouldn't work here...
+
+Any ideas or insights?
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/381a3158-6635-452c-a270-247df28a6dae)
+
+
+The above can be found if creating a `flow/settings.mk` file:
+
+```
+export DESIGN_CONFIG?=designs/asap7/mock-array/config.mk
+export MOCK_ARRAY_DATAWIDTH?=8
+export MOCK_ARRAY_TABLE?=8 8 4 4 5 5
+export MOCK_ARRAY_SCALE?=80
+```
+
+and running `make verilog` and `make`
+
+
+Various interesting things can be seen in detailed routing:
+
+- almost all the wires are vertical/horizontal between "Element" macros. The loop above is untypical, usually it's just a slight horizontal/vertical deviation.
+- there are hold cells in the middle to the right
+
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/e9bca2da-5e41-4ee6-b279-e7ca375bb26a)
+
+
+
+Hold cells have to be placed *outside* to the right of the array, hence many non-vertical vertical wires between those two elements.
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/3a17be46-8604-498c-901f-ce375cbed5cc)
+
+
+### maliberty
+@osamahammad21 any thoughts on the loop?
+
+### oharboe
+A feature request filed: https://github.com/The-OpenROAD-Project/OpenROAD/issues/3634
+

Bug/4163.md

@@ -0,0 +1,29 @@
+# [WARNING GRT-0350] Missing route to pin iregister_read/io_bypass_1_bits_data[0].
+
+Tool: Global Routing
+
+Subcategory: Parasitics estimation issue
+
+## Conversation
+
+### oharboe
+This is for the top level of MegaBoom that I'm playing around with.
+
+Is this warning telling me that it can't find a route for the buffer tree for the pin in the warning?
+
+It looks like this buffer tree is going from the iregister_read macro to the ALUExeUnit, which traverses Rob(reorder buffer), rename stage and the memory issue unit. The mpl2 macro placement is unfortunate here...
+
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/e3c6b965-bf83-403c-9dd5-70413735a8ca)
+
+
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/c2a76f06-f286-4b5a-8bc7-2fc0219bc9f8)
+
+
+### maliberty
+@eder-matheus please respond
+
+### eder-matheus
+@oharboe @maliberty This warning is related to the estimate_parasitics using global route parasitics. It usually happens when a routing topology is not correctly translated to the parasitics estimation structures. I will look into the test case and fix the cause of this bug.
+

Bug/4845.md

@@ -0,0 +1,34 @@
+# Is [read_def -floorplan_initialize ] expected to unset [set_max_transition] and [set_max_capacitance] from sdc file?
+
+Tool: Initialize Floorplan
+
+Subcategory: Unexpected behavior
+
+## Conversation
+
+### b62833
+Before I file a bug, I want to make sure this is unexpected behavior.
+
+In my sdc file I do a 
+```
+
+set_max_transition [exp $clk_period * 0.20] [current_design]
+set_max_capacitance 30 [current_design]
+```
+
+and then read a floorplan by setting FLOORPLAN_DEF.
+
+When I run through floorplanning, 2_floorplan.sdc doesn't have those commands. I've narrowed it down to floorplan.tcl's `read_def -floorplan_initialize` that's removing these. Max transition and max capacitance can't be set in DEF if I remember correctly, so this is unexpected. Is this the desired tool behavior?
+
+
+
+### maliberty
+I would consider it unexpected so go ahead and open an issue with a test case
+
+### b62833
+Over the weekend I upgraded to OpenROAD version 2.0-13286-gebcc5196e and it works now.
+
+It was broken in the version v2.0-11493-gaddecc2bd that I'd been using before.
+
+We're good now.
+

Bug/5333.md

@@ -0,0 +1,48 @@
+# pdgen remove stripes with [WARNING PDN-0200] Removing floating shape:
+
+Tool: Power Distribution Network Generator
+
+Subcategory: Power distribution network issue
+
+## Conversation
+
+### titan73
+Based on the example at the bottom of https://openroad.readthedocs.io/en/latest/main/src/pdn/README.html.
+
+I did the following floorplan with the .def containing the power pins:
+
+    read_def -floorplan_initialize floor.def
+    set fp_area [ord::get_die_area]
+    initialize_floorplan -die_area $fp_area -core_area $fp_area -site CORECUBRICK
+
+    add_global_connection -net VDDD -pin_pattern {^VDDD$} -power
+    add_global_connection -net GNDD -pin_pattern {^GNDD$} -ground
+
+    set_voltage_domain -power VDDD -ground GNDD
+
+    define_pdn_grid -name "Core"
+    add_pdn_ring -grid "Core" -layers {metal4B alucap} -widths 5.0 -spacings 2.0 -core_offsets 4.5 -connect_to_pads
+
+    add_pdn_stripe -followpins -layer metal1 -extend_to_core_ring
+
+    add_pdn_stripe -layer metal4B -width 0.48 -pitch 56.0 -offset 2.0 -extend_to_core_ring
+    add_pdn_stripe -layer alucap -width 1.40 -pitch 40.0 -offset 2.0 -extend_to_core_ring
+
+    add_pdn_connect -layers {metal4B alucap}
+    add_pdn_connect -layers {alucap metal4B}
+
+    pdngen
+
+The sroutes and the ring are created but not the stripes and I get the the warnings:
+
+    [WARNING PDN-0200] Removing floating shape: GNDD (1.7600, -9.5000) - (2.2400, 821.3000) on metal4B
+    [WARNING PDN-0200] Removing floating shape: VDDD (29.7600, -16.5000) - (30.2400, 828.3000) on metal4B
+
+Is there something more to do to connect these shapes?
+
+### titan73
+Also note that the related power pins imported the from .def are removed.
+
+### maliberty
+Can you provide a test case?  Its hard to say much from just the output
+

Build/1951.md

@@ -0,0 +1,25 @@
+# Is it possible to generate a static binary of OpenROAD?
+
+Subcategory: Static binary generation
+
+## Conversation
+
+### TiagoAFontana
+Hi all, I am trying to execute the OpenROAD in a cluster machine. However, in this machine, I am not able to install the dependencies to compile the OpenROAD or even use the docker image to run the OpenROAD.
+
+I was wondering if it is possible to set a cmake flag to generate a static binary (without any dependencies) for the OpenROAD project. With this, I will be able to run this binary on every machine that I need.
+
+Does someone know how to do this? 
+
+### vijayank88
+@vvbandeira  Any suggestion?
+
+### QuantamHD
+Bazel rules hdl supports fully static builds of openroad.
+
+Just download bazel, git clone https://github.com/hdl/bazel_rules_hdl
+
+And run bazel build @org_theopenroadproject//:openroad in the git repo. 
+
+It also statically builds the entire dependency chain of openroad from source.
+

Build/2330.md

@@ -0,0 +1,50 @@
+# Compilation Error
+
+Subcategory: Compilation error
+
+## Conversation
+
+### gudeh
+Hey guys! I am getting the following compilation error:
+
+> [100%] Linking CXX executable openroad
+> cd /home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build/src && /usr/local/bin/cmake -E cmake_link_script CMakeFiles/openroad.dir/link.txt --verbose=1
+> /usr/bin/c++  -O3 -DNDEBUG  -Wl,--export-dynamic -rdynamic CMakeFiles/openroad.dir/Design.cc.o CMakeFiles/openroad.dir/Tech.cc.o CMakeFiles/openroad.dir/OpenRoad.cc.o CMakeFiles/openroad.dir/Main.cc.o  -o openroad ifp/src/ifp.a openroad_swig.a gpl/gpl.a dpl/dpl.a dpo/dpo.a fin/fin.a rsz/src/rsz.a ppl/ppl.a stt/stt.a dbSta/src/dbSta.a ../../src/sta/app/libOpenSTA.a odb/src/db/libodb.a odb/src/swig/tcl/odbtcl.a rcx/src/rcx.a rmp/src/rmp.a cts/src/cts.a grt/grt.a tap/src/tap.a gui/gui.a drt/drt.a dst/dst.a mpl/mpl.a mpl2/mpl2.a psm/src/psm.a ant/src/ant.a par/par.a utl/utl.a pdn/src/pdn.a ../third-party/abc/libabc.a /usr/lib/x86_64-linux-gnu/libtcl.so -lpthread /usr/lib/x86_64-linux-gnu/libtclreadline.so /usr/lib/x86_64-linux-gnu/libz.so _openroad_swig_py.a odb/src/swig/python/_odbpy.a ifp/src/_ifp_py.a /usr/lib/x86_64-linux-gnu/librt.so ppl/src/munkres/libMunkres.a -lm -ldl -lrt rsz/src/rsz.a grt/grt.a ant/src/ant.a grt/grt.a ant/src/ant.a dpl/dpl.a grt/src/fastroute/libFastRoute4.1.a stt/stt.a sta/sta_swig.a /usr/local/lib/libboost_serialization.a /usr/local/lib/libboost_system.a /usr/local/lib/libboost_thread.a /usr/lib/gcc/x86_64-linux-gnu/9/libgomp.so /usr/lib/x86_64-linux-gnu/libpthread.so /usr/local/lib/libboost_serialization.a mpl/src/ParquetFP/libParquetFP.a par/src/MLPart/libMLPart.a dbSta/src/dbSta.a gui/gui.a /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8 ../../src/sta/app/libOpenSTA.a odb/src/db/libodb.a odb/src/defout/libdefout.a odb/src/lefout/liblefout.a odb/src/tm/libtm.a /usr/lib/x86_64-linux-gnu/libtcl.so odb/src/cdl/libcdl.a odb/src/swig/common/libodb_swig_common.a odb/src/defin/libdefin.a odb/src/def/libdef.a odb/src/def/libdefzlib.a odb/src/lefin/liblefin.a odb/src/zutil/libzutil.a utl/utl.a /usr/local/lib/libspdlog.a -lpthread odb/src/lef/liblef.a odb/src/lef/liblefzlib.a /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libpython3.8.so 
+> /usr/bin/ld: drt/drt.a(TritonRoute.cpp.o): in function \`boost::archive::basic_binary_iarchive<fr::frIArchive>::init()':
+> TritonRoute.cpp:(.text._ZN5boost7archive21basic_binary_iarchiveIN2fr10frIArchiveEE4initEv[_ZN5boost7archive21basic_binary_iarchiveIN2fr10frIArchiveEE4initEv]+0xc4): undefined reference to `boost::archive::detail::basic_iarchive::set_library_version(boost::archive::library_version_type)'
+> collect2: error: ld returned 1 exit status
+> make[2]: *** [src/CMakeFiles/openroad.dir/build.make:210: src/openroad] Error 1
+> make[2]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
+> make[1]: *** [CMakeFiles/Makefile2:449: src/CMakeFiles/openroad.dir/all] Error 2
+> make[1]: *** Waiting for unfinished jobs....
+> [100%] Linking CXX executable trTest
+> cd /home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build/src/drt && /usr/local/bin/cmake -E cmake_link_script CMakeFiles/trTest.dir/link.txt --verbose=1
+> /usr/bin/c++  -O3 -DNDEBUG   CMakeFiles/trTest.dir/test/gcTest.cpp.o CMakeFiles/trTest.dir/test/fixture.cpp.o CMakeFiles/trTest.dir/test/stubs.cpp.o CMakeFiles/trTest.dir/__/gui/src/stub.cpp.o  -o trTest drt.a ../odb/src/db/libodb.a ../stt/stt.a ../dst/dst.a ../sta/sta_swig.a /usr/local/lib/libboost_serialization.a /usr/local/lib/libboost_system.a /usr/local/lib/libboost_thread.a ../dbSta/src/dbSta.a ../gui/gui.a ../odb/src/db/libodb.a ../odb/src/cdl/libcdl.a ../odb/src/defin/libdefin.a ../odb/src/def/libdef.a ../odb/src/def/libdefzlib.a ../odb/src/defout/libdefout.a ../odb/src/lefin/liblefin.a ../odb/src/lef/liblef.a ../odb/src/lef/liblefzlib.a ../odb/src/lefout/liblefout.a ../odb/src/tm/libtm.a ../odb/src/zutil/libzutil.a /usr/lib/x86_64-linux-gnu/libtcl.so /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8 ../../../src/sta/app/libOpenSTA.a ../utl/utl.a /usr/local/lib/libspdlog.a -lpthread /usr/lib/gcc/x86_64-linux-gnu/9/libgomp.so /usr/lib/x86_64-linux-gnu/libpthread.so /usr/local/lib/libboost_serialization.a /usr/lib/x86_64-linux-gnu/libz.so 
+> make[2]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
+> [100%] Built target trTest
+> make[1]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
+> make: *** [Makefile:133: all] Error 2
+
+The error I pasted here is from a clean clone from the flow repository. I did the following commands to get to this error:
+
+> git clone --recursive https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts
+> cd OpenROAD-flow-scripts
+> sudo ./tools/OpenROAD/etc/DependencyInstaller.sh -dev
+> ./build_openroad.sh --local
+
+I noticed that if I run DepdencyInstaller multiple times it actually updates and compile Boost everytime. Not sure how to proceed, any help is welcome.
+
+### maliberty
+What OS and what compiler?
+
+### maliberty
+The log unfortunately doesn't have the boost version so I just added print that in the OR master branch.  What version of boost do you have installed?
+
+### gudeh
+Hi everyone, I was able to solve the issue by manually updating Boost. I used the links from [this stackoverflow page](https://stackoverflow.com/questions/2829523/upgrading-boost-version) and set the "-prefix=" with the same location my Boost was already installed. Also, I had to clean my previous build from OR.
+
+It seems that for some reason the DependencyInstaller didn't fetch the correct Boost version to upgrade to.
+
+### maliberty
+@vvbandeira any idea about " for some reason the DependencyInstaller didn't fetch the correct Boost version to upgrade to."?
+

Build/2342.md

@@ -0,0 +1,51 @@
+# Apple clang 14.0.0 (Xcode 14.0.1) M1 coredumps compiling abc .c files
+
+Tool: ABC
+
+Subcategory: Compiler crash
+
+## Conversation
+
+### stefanottili
+Hi Folks,
+
+just a heads up for anybody using an Apple M1 with the most recent Xcode 14.0.1
+
+Apple clang 14.0.0 randomly coredumps compiling abc .c files. But not deterministically, restarting ./build_openroad.sh will eventually compile some of them til it finally always coredumps compiling extraUtilMisc.c.
+
+I was able to compile OpenROAD on this machine before, but not with the latest and greatest Xcode.
+
+I'm curious whether there are other M1/Xcode users out there with similar experience.
+
+Stefan
+
+gmake[2]: Entering directory '/Users/user/OpenROAD-flow-scripts/tools/OpenROAD/build'
+[  0%] Building CXX object third-party/abc/CMakeFiles/libabc.dir/src/misc/extra/extraUtilMisc.c.o
+cd /Users/user/OpenROAD-flow-scripts/tools/OpenROAD/build/third-party/abc && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -I/Users/user/OpenROAD-flow-scripts/tools/OpenROAD/third-party/abc/src -O3 -DNDEBUG -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -Wall -Wno-array-bounds -Wno-nonnull -Wno-unused-variable -Wno-unused-function -Wno-write-strings -Wno-sign-compare -Wno-deprecated -Wno-c++11-narrowing -Wno-register -Wno-format -Wno-reserved-user-defined-literal -DABC_USE_STDINT_H=1 -DABC_MEMALIGN=4 -DABC_NAMESPACE=abc -fpermissive -DABC_USE_CUDD=1 -DABC_USE_PTHREADS -Wno-unused-but-set-variable -std=c++17 -MD -MT third-party/abc/CMakeFiles/libabc.dir/src/misc/extra/extraUtilMisc.c.o -MF CMakeFiles/libabc.dir/src/misc/extra/extraUtilMisc.c.o.d -o CMakeFiles/libabc.dir/src/misc/extra/extraUtilMisc.c.o -c /Users/user/OpenROAD-flow-scripts/tools/OpenROAD/third-party/abc/src/misc/extra/extraUtilMisc.c
+clang: error: unable to execute command: Segmentation fault: 11
+clang: error: clang frontend command failed due to signal (use -v to see invocation)
+Apple clang version 14.0.0 (clang-1400.0.29.102)
+Target: arm64-apple-darwin21.6.0
+Thread model: posix
+InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
+
+
+### stefanottili
+downgrading the command line tools to 13.4 allows to build the project
+
+### stefanottili
+Here's some feedback from https://developer.apple.com/forums/thread/717259
+
+> It only happens with optimized code. An alternative workaround for building openroad is to patch the abc cmake file to include -g
+
+third-party/CMakeLists.txt @@ -46,6 +46,10 @@ if (NOT USE_SYSTEM_ABC)
+readline is not needed since we call abc from c++
+set(READLINE_FOUND FALSE)
++# apple clang 14.0.0 seg faults on abc without -g +add_compile_options(
+$<$<CXX_COMPILER_ID:AppleClang>:-g>
++) add_subdirectory(abc)
+endif()
+
+### stefanottili
+clang-1400.0.29.202 as part of Xcode 14.1.0 compiles OpenRoad without issues
+

Build/2952.md

@@ -0,0 +1,104 @@
+# Cannot build with CUDA
+
+Tool: Verilog to DB
+
+Subcategory: Compiler version mismatch
+
+## Conversation
+
+### yathAg
+I am trying to build Openroad with cmake .. -DGPU=true and I get the following output
+
+```
+-- GPU is enabled
+-- CUDA is found
+-- The CUDA compiler identification is NVIDIA 10.1.243
+-- Detecting CUDA compiler ABI info
+-- Detecting CUDA compiler ABI info - done
+-- Check for working CUDA compiler: /usr/bin/nvcc - skipped
+-- Detecting CUDA compile features
+-- Detecting CUDA compile features - done
+-- Found re2: /opt/or-tools/lib/cmake/re2/re2Config.cmake (found version "9.0.0") 
+-- Found Clp: /opt/or-tools/lib/cmake/Clp/ClpConfig.cmake (found version "1.17.7") 
+-- Found Cbc: /opt/or-tools/lib/cmake/Cbc/CbcConfig.cmake (found version "2.10.7") 
+-- Found Eigen3: /usr/local/share/eigen3/cmake/Eigen3Config.cmake (found version "3.4.0") 
+-- Found SCIP: /opt/or-tools/lib/cmake/scip/scip-config.cmake (found version "8.0.1") 
+-- GUI is enabled
+-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization 
+-- Found OpenMP_CXX: -fopenmp (found version "4.5") 
+-- Found OpenMP: TRUE (found version "4.5")  
+-- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS) 
+-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found suitable version "1.80.0", minimum required is "1.78")  
+-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization system thread 
+-- TCL readline enabled
+-- Tcl Extended disabled
+-- Python3 enabled
+-- Configuring done
+CMake Warning (dev) in src/gpl/CMakeLists.txt:
+  Policy CMP0104 is not set: CMAKE_CUDA_ARCHITECTURES now detected for NVCC,
+  empty CUDA_ARCHITECTURES not allowed.  Run "cmake --help-policy CMP0104"
+  for policy details.  Use the cmake_policy command to set the policy and
+  suppress this warning.
+
+  CUDA_ARCHITECTURES is empty for target "gpl".
+This warning is for project developers.  Use -Wno-dev to suppress it.
+
+CMake Error in src/gpl/CMakeLists.txt:
+  Target "gpl" requires the language dialect "CUDA17" .  But the current
+  compiler "NVIDIA" does not support this, or CMake does not know the flags
+  to enable it.
+
+
+-- Generating done
+CMake Generate step failed.  Build files cannot be regenerated correctly.
+```
+
+I have Cuda installed and on `nvidia-smi` I get 
+
+```
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 525.85.12    Driver Version: 525.85.12    CUDA Version: 12.0     |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|                               |                      |               MIG M. |
+|===============================+======================+======================|
+|   0  NVIDIA GeForce ...  On   | 00000000:01:00.0  On |                  N/A |
+| N/A   51C    P5    18W / 115W |    187MiB /  6144MiB |     19%      Default |
+|                               |                      |                  N/A |
++-------------------------------+----------------------+----------------------+
+                                                                               
++-----------------------------------------------------------------------------+
+| Processes:                                                                  |
+|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
+|        ID   ID                                                   Usage      |
+|=============================================================================|
+|    0   N/A  N/A      1211      G   /usr/lib/xorg/Xorg                 52MiB |
+|    0   N/A  N/A      1875      G   /usr/lib/xorg/Xorg                133MiB |
++-----------------------------------------------------------------------------+
+```
+
+and on `nvcc -V`
+
+```
+nvcc: NVIDIA (R) Cuda compiler driver
+Copyright (c) 2005-2019 NVIDIA Corporation
+Built on Sun_Jul_28_19:07:16_PDT_2019
+Cuda compilation tools, release 10.1, V10.1.243
+```
+Any help on how to get the setup working is really appreciated and thanks in advanced.
+
+
+
+
+
+
+
+### vvbandeira
+Please install a newer version of `nvcc` and try again. As per NVIDIA docs, you will require at least v11; see more [here](https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#c-17-language-features).
+
+### maliberty
+If we bump to cmake 3.10 then https://cmake.org/cmake/help/latest/module/FindCUDA.html suggests we can use the usual VERSION keyword.
+
+FYI - the use of CUDA is quite minimal and probably not worth the bother at this point.
+

Build/3094.md

@@ -0,0 +1,50 @@
+# Problems with etc/DependencyInstaller.sh and md5 on boost
+
+Subcategory: Dependency installation
+
+## Conversation
+
+### oharboe
+What's going on here?
+
+```bash
+$ etc/DependencyInstaller.sh -prefix=~/openroad-tools/ -common
+[deleted]
+Length: 136670223 (130M) [application/x-gzip]
+Saving to: ‘boost_1_80_0.tar.gz.1’
+
+boost_1_80_0.tar.gz 100%[===================>] 130,34M  2,37MB/s    in 65s
+
+2023-03-27 16:56:06 (2,02 MB/s) - ‘boost_1_80_0.tar.gz.1’ saved [136670223/136670223]
+
++ md5sum -c /dev/fd/63
+++ echo '077f074743ea7b0cb49c6ed43953ae95  boost_1_80_0.tar.gz'
+boost_1_80_0.tar.gz: FAILED
+md5sum: WARNING: 1 computed checksum did NOT match
++ exit 1
+```
+
+### oharboe
+Hmm.... I suspect a manifestation of https://github.com/The-OpenROAD-Project/OpenROAD/issues/3096
+
+### vvbandeira
+The problem is that the first download failed, and the file was not correctly deleted.
+
+New download:
+```
+boost_1_80_0.tar.gz 100%[===================>] 130,34M  2,37MB/s    in 65s
+```
+
+Saving with the `.1` suffix:
+```
+2023-03-27 16:56:06 (2,02 MB/s) - ‘boost_1_80_0.tar.gz.1’ saved [136670223/136670223]
+```
+
+Checking against the file without the suffix:
+```
++ md5sum -c /dev/fd/63
+++ echo '077f074743ea7b0cb49c6ed43953ae95  boost_1_80_0.tar.gz'
+```
+
+I will propose a PR that uses `mktemp` that should avoid this and the #3096 issues. You can manually delete the folder/offending file for now -- apologies for the inconvenience.
+

Build/3124.md

@@ -0,0 +1,43 @@
+# Problems building - undefined reference to `ord::getLogger()'
+
+Subcategory: Compilation error
+
+## Conversation
+
+### oharboe
+Any idea what is going on here?
+
+```
+./build_openroad.sh --local --openroad-args "-D CMAKE_BUILD_TYPE=RELEASE"
+[deleted]
+TIMEOUT=5 -D TEST_XML_OUTPUT_DIR= -P /home/oyvind/ascenium/OpenROAD-flow-scripts/dependencies/share/cmake-3.24/Modules/GoogleTestAddTests.cmake
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::report(char const*)':
+LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::open_metrics(char const*)':
+LoggerCommon.cpp:(.text+0x2e9): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::close_metrics(char const*)':
+LoggerCommon.cpp:(.text+0x309): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::set_metrics_stage(char const*)':
+LoggerCommon.cpp:(.text+0x32e): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::clear_metrics_stage()':
+LoggerCommon.cpp:(.text+0x369): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o):LoggerCommon.cpp:(.text+0x38e): more undefined references to `ord::getLogger()' follow
+collect2: error: ld returned 1 exit status
+```
+
+### vijayank88
+@oharboe 
+Have you removed `OpenROAD-flow-scripts/tools` directory before building again.
+Sometimes it may cause the issue.
+@vvbandeira Can please check this?
+
+### maliberty
+which binary is it building when the error happens?
+
+### oharboe
+Rejoice! I finally got it to compile. I deleted the *entire* ORFS folder, recloned, reran sudo ./setup.sh and then the build worked.
+
+So, somewhere inside the ORFS folder there was an out of date file that wasn't being built...
+
+It would be nice to know what exactly is going wrong, but I guess that will have to wait until next time it breaks and I do some more investigations?
+

Build/3148.md

@@ -0,0 +1,51 @@
+# LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
+
+Subcategory: Linking error
+
+## Conversation
+
+### oharboe
+I'm getting this problem again while building OpenROAD locally.  I've tried recloning and deleting the entire ORFS folder, still no luck.
+
+Any ideas?
+
+```
+$ lsb_release -a
+No LSB modules are available.
+Distributor ID:	Ubuntu
+Description:	Ubuntu 22.10
+Release:	22.10
+Codename:	kinetic
+
+```
+```
+./build_openroad.sh --local --openroad-args "-D CMAKE_BUILD_TYPE=RELEASE"
+```
+
+```
+[deleted]
+FAILED: src/dpl/test/dpl_test src/dpl/test/dpl_test[1]_tests.cmake /home/oyvind/ascenium/blah/tools/OpenROAD/build/src/dpl/test/dpl_test[1]_tests.cmake 
+: && /usr/bin/c++ -O3 -DNDEBUG  src/dpl/test/CMakeFiles/dpl_test.dir/dpl_test.cc.o -o src/dpl/test/dpl_test  -lgtest  -lgtest_main  src/dpl/libdpl_lib.a  src/odb/src/cdl/libcdl.a  src/odb/src/defin/libdefin.a  src/odb/src/def/libdef.a  src/odb/src/def/libdefzlib.a  src/odb/src/lefin/liblefin.a  src/odb/src/lef/liblef.a  src/odb/src/lef/liblefzlib.a  /usr/lib/x86_64-linux-gnu/libz.so  src/odb/src/db/libdb.a  src/odb/src/defout/libdefout.a  src/odb/src/lefout/liblefout.a  src/odb/src/zutil/libzutil.a  src/odb/src/db/libdb.a  src/odb/src/defout/libdefout.a  src/odb/src/lefout/liblefout.a  src/odb/src/zutil/libzutil.a  src/odb/src/tm/libtm.a  /home/oyvind/ascenium/blah/tools/OpenROAD/src/sta/app/libOpenSTA.a  /usr/lib/x86_64-linux-gnu/libtcl.so  /usr/lib/x86_64-linux-gnu/libtclreadline.so  /usr/lib/x86_64-linux-gnu/libz.so  -ltcl  src/utl/utl.a  src/utl/libutl_lib.a  /home/oyvind/ascenium/blah/dependencies/lib/libspdlog.a && cd /home/oyvind/ascenium/blah/tools/OpenROAD/build/src/dpl/test && /home/oyvind/ascenium/blah/dependencies/bin/cmake -D TEST_TARGET=dpl_test -D TEST_EXECUTABLE=/home/oyvind/ascenium/blah/tools/OpenROAD/build/src/dpl/test/dpl_test -D TEST_EXECUTOR= -D TEST_WORKING_DIR=/home/oyvind/ascenium/blah/tools/OpenROAD/src/dpl/test -D TEST_EXTRA_ARGS= -D TEST_PROPERTIES= -D TEST_PREFIX= -D TEST_SUFFIX= -D TEST_FILTER= -D NO_PRETTY_TYPES=FALSE -D NO_PRETTY_VALUES=FALSE -D TEST_LIST=dpl_test_TESTS -D CTEST_FILE=/home/oyvind/ascenium/blah/tools/OpenROAD/build/src/dpl/test/dpl_test[1]_tests.cmake -D TEST_DISCOVERY_TIMEOUT=5 -D TEST_XML_OUTPUT_DIR= -P /home/oyvind/ascenium/blah/dependencies/share/cmake-3.24/Modules/GoogleTestAddTests.cmake
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::report(char const*)':
+LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::open_metrics(char const*)':
+LoggerCommon.cpp:(.text+0x2e9): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::close_metrics(char const*)':
+LoggerCommon.cpp:(.text+0x309): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::set_metrics_stage(char const*)':
+LoggerCommon.cpp:(.text+0x32e): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::clear_metrics_stage()':
+LoggerCommon.cpp:(.text+0x369): undefined reference to `ord::getLogger()'
+/usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o):LoggerCommon.cpp:(.text+0x38e): more undefined references to `ord::getLogger()' follow
+collect2: error: ld returned 1 exit status
+[3/39] Automatic MOC and UIC for target gui
+ninja: build stopped: subcommand failed.
+```
+
+
+### maliberty
+I can't reproduce it but can you try changing https://github.com/The-OpenROAD-Project/OpenROAD/blob/8a49dff86645352d30780951b1146b31ef41b0f4/src/dpl/CMakeLists.txt#L58 to utl_lib and see if that helps.
+
+### maliberty
+PR coming.  I'm not sure why it varies - perhaps different compilers?
+

Build/3489.md

@@ -0,0 +1,26 @@
+# ABC contains local modifications!
+
+Tool: Verilog to DB
+
+Subcategory: Compilation error
+
+## Conversation
+
+### Simonliudan
+[ 12%] Building abc/abc-bafd2a7
+Debug: ABCREV=bafd2a7
+[ 22%] Building passes/techmap/filterlib.o
+[ 22%] Building yosys-smtbmc
+ERROR: ABC contains local modifications! Set ABCREV=default in Yosys Makefile!
+make: *** [Makefile:749: abc/abc-bafd2a7] Error 1
+
+in Centos, I have set ABCREV = default, but the debug info is bafd2a7
+
+
+### vijayank88
+Is this installation issue?
+Can you provide steps to reproduce the same?
+
+### vvbandeira
+@Simonliudan, this looks more like an issue than a discussion. Please file an Issue and follow the Issue template, the template give us important information to help you.
+

Build/3513.md

@@ -0,0 +1,33 @@
+# Build problems. Missing gmock.h
+
+Subcategory: Missing dependency
+
+## Conversation
+
+### oharboe
+There has been a lot of activity concerning build errors, but I tried with latest master merged with #3512
+
+Is it enough to update to latest master or do I need to purge something or other locally?
+
+```
+./build_openroad.sh --local --openroad-args "-DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_CXX_FLAGS=-g"
+```
+
+```
+[ 25%] Building CXX object src/odb/test/cpp/CMakeFiles/TestGuide.dir/TestGuide.cpp.o
+/home/oyvind/OpenROAD-flow-scripts/tools/OpenROAD/src/odb/test/cpp/TestAbstractLef.cc:13:10: fatal error: gmock/gmock.h: No such file or directory
+   13 | #include "gmock/gmock.h"
+      |          ^~~~~~~~~~~~~~~
+compilation terminated.
+gmake[2]: *** [src/odb/test/cpp/CMakeFiles/OdbGTests.dir/build.make:90: src/odb/test/cpp/CMakeFiles/OdbGTests.dir/TestAbstractLef.cc.o] Error 1
+gmake[1]: *** [CMakeFiles/Makefile2:2331: src/odb/test/cpp/CMakeFiles/OdbGTests.dir/all] Error 2
+gmake[1]: *** Waiting for unfinished jobs...
+```
+
+
+### QuantamHD
+This ones my bad. It seems that some installations of libgtest-dev don't include google mock. If you uninstall your system gtest it will fix this error, but I'll see if there's something else we could do to fix this.
+
+### vvbandeira
+Fixed on #3514 
+

Build/3779.md

@@ -0,0 +1,19 @@
+# arm64 release for Ubuntu
+
+Subcategory: Cross-platform compilation
+
+## Conversation
+
+### ilyaext
+I'm looking for an arm64 OpenROAD architecture release to install on Linux AWS EC2 arm64.
+Can anyone give me a link or suggest how to compile?
+
+### maliberty
+We don't test or release on arm64 but you can probably build from source.
+
+### maliberty
+https://openroad.readthedocs.io/en/latest/user/Build.html
+
+### maliberty
+https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildLocally.html for ORFS
+

Build/4137.md

@@ -0,0 +1,1565 @@
+# OpenROAD build issue
+
+Subcategory: Compilation error
+
+## Conversation
+
+### idokoike
+
+I've been trying to fully install OpenROAD using the` ./build_openroad.sh --local --threads 1` command but I keep getting the error
+```
+[INFO FLW-0027] Saving logs to build_openroad.log
+[INFO FLW-0028] ./build_openroad.sh --local --threads 1
+[INFO FLW-0002] Updating git submodules.
+[INFO FLW-0001] Using local build method. This will create binaries at 'tools/install' unless overwritten.
+[INFO FLW-0017] Compiling Yosys.
+make: Entering directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
+mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
+cp yosys yosys-config yosys-abc yosys-filterlib yosys-smtbmc /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
+strip -S /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys
+strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-abc
+strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-filterlib
+mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys
+cp -r share/. /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys/.
+make: Leaving directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
+[INFO FLW-0018] Compiling OpenROAD.
+-- OpenROAD version: v2.0-10669-g436c7801a
+-- System name: Linux
+-- Compiler: GNU 11.4.0
+-- Build type: RELEASE
+-- Install prefix: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
+-- C++ Standard: 17
+-- C++ Standard Required: ON
+-- C++ Extensions: OFF
+-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
+-- TCL header: /usr/include/tcl/tcl.h
+-- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
+-- TCL readline header: /usr/include/x86_64-linux-gnu
+-- boost: 1.74.0
+-- spdlog: 1.9.2
+CMake Warning at src/CMakeLists.txt:242 (message):
+  spdlog: SPDLOG_FMT_EXTERNAL=ON
+
+
+-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) 
+-- STA version: 2.4.0
+-- STA git sha: 44f06c521560e803859218732255b3259de048e1
+-- System name: Linux
+-- Compiler: GNU 11.4.0
+-- Build type: RELEASE
+-- Build CXX_FLAGS: -O3 -DNDEBUG
+-- Install prefix: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
+-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
+-- TCL header: /usr/include/tcl/tcl.h
+-- SSTA: 0
+-- STA executable: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/OpenROAD/src/sta/app/sta
+CMake Error at src/gpl/CMakeLists.txt:44 (find_package):
+  By not providing "Findortools.cmake" in CMAKE_MODULE_PATH this project has
+  asked CMake to find a package configuration file provided by "ortools", but
+  CMake did not find one.
+
+  Could not find a package configuration file provided by "ortools" with any
+  of the following names:
+
+    ortoolsConfig.cmake
+    ortools-config.cmake
+
+  Add the installation prefix of "ortools" to CMAKE_PREFIX_PATH or set
+  "ortools_DIR" to a directory containing one of the above files.  If
+  "ortools" provides a separate development package or SDK, be sure it has
+  been installed.
+
+
+-- Configuring incomplete, errors occurred!
+
+```
+I've installed or-tools using `git clone  https://github.com/google/or-tools.git` and I'm still getting the error 
+
+### rovinski
+This is better to submit as an issue in order to get a better handle on your environment.
+
+That being said, where are you installing ortools? The default location that CMake looks for is the default paths searched by CMake's `find_package` and also `/opt/or-tools/lib64/` and `/opt/or-tools/lib/`. If it's not in one of those locations, you should either install it there, or add `--openroad-args "ortools_DIR=path/to/your/ortools/cmake/file"` to your script invocation.
+
+### idokoike
+Thanks. I've added `--openroad-args "ortools_DIR=path/to/your/ortools/cmake/file"` to my script, and it works kind of but I'm getting another error
+
+```
+[INFO FLW-0027] Saving logs to build_openroad.log
+[INFO FLW-0028] ./build_openroad.sh --local threads 2 --openroad-args /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build
+[INFO FLW-0002] Updating git submodules.
+[INFO FLW-0001] Using local build method. This will create binaries at 'tools/install' unless overwritten.
+[INFO FLW-0017] Compiling Yosys.
+make: Entering directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
+mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
+cp yosys yosys-config yosys-abc yosys-filterlib yosys-smtbmc /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
+strip -S /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys
+strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-abc
+strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-filterlib
+mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys
+cp -r share/. /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys/.
+make: Leaving directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
+[INFO FLW-0018] Compiling OpenROAD.
+-- ortools version: 9.7.3002
+-- Build type: Release
+-- Build C++ library: ON
+-- Build Python: OFF
+-- Build Java: OFF
+-- Build .Net: OFF
+-- Build Flatzinc: ON
+-- Build LP Parser: ON
+-- Build standalone Glop: OFF
+-- Build samples: ON
+-- Build C++ samples: ON
+-- Build Python samples: OFF
+-- Build Java samples: OFF
+-- Build .Net samples: OFF
+-- Build examples: ON
+-- Build C++ examples: ON
+-- Build Python examples: OFF
+-- Build Java examples: OFF
+-- Build .Net examples: OFF
+-- Build documentation: OFF
+-- Install doc: OFF
+-- Build all dependencies: ON
+-- Build ZLIB: ON
+-- Build abseil-cpp: ON
+-- Build protobuf: ON
+-- Build re2: ON
+-- Build googletest: ON
+-- COIN-OR support: OFF
+-- GLPK support: OFF
+-- HiGHS support: OFF
+-- PDLP support: ON
+-- Build PDLP: ON
+-- Build eigen3: ON
+-- SCIP support: OFF
+-- CPLEX support: OFF
+-- XPRESS support: OFF
+-- C++: Build doc: OFF
+-- Fetching ZLIB
+--   Populating zlib
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/zlib-subbuild
+[100%] Built target zlib-populate
+-- Fetching ZLIB - fetched
+-- Fetching Abseil-cpp
+--   Populating absl
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/absl-subbuild
+[100%] Built target absl-populate
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:605 (message):
+  ABSL_CXX_STANDARD:
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMakeLists.txt:86 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:606 (message):
+  CMAKE_CXX_STANDARD: 17
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMakeLists.txt:86 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:607 (message):
+  CMAKE_CXX_STANDARD_REQUIRED: ON
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMakeLists.txt:86 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:608 (message):
+  CMAKE_CXX_FLAGS:
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMakeLists.txt:86 (include)
+
+
+CMake Warning at build/_deps/absl-src/absl/copts/AbseilConfigureCopts.cmake:97 (message):
+  ABSL_CXX_STANDARD: 17.
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMake/AbseilHelpers.cmake:18 (include)
+  build/_deps/absl-src/CMakeLists.txt:87 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:605 (message):
+  ABSL_CXX_STANDARD: 17
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
+  build/_deps/absl-src/CMakeLists.txt:87 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:606 (message):
+  CMAKE_CXX_STANDARD: 17
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
+  build/_deps/absl-src/CMakeLists.txt:87 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:607 (message):
+  CMAKE_CXX_STANDARD_REQUIRED: ON
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
+  build/_deps/absl-src/CMakeLists.txt:87 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:608 (message):
+  CMAKE_CXX_FLAGS:
+Call Stack (most recent call first):
+  build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
+  build/_deps/absl-src/CMakeLists.txt:87 (include)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:20 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:33 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:44 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:58 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:76 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:95 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:107 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:121 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:140 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:161 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:177 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:220 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:249 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:428 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:539 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:591 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:623 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/base/CMakeLists.txt:649 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/algorithm/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/algorithm/CMakeLists.txt:42 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/cleanup/CMakeLists.txt:16 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/cleanup/CMakeLists.txt:30 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:91 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:120 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:170 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:186 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:204 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:277 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:313 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:351 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:387 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:423 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:453 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:530 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:556 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:581 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:613 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:625 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:638 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:664 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:679 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:691 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/container/CMakeLists.txt:760 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:16 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:31 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:56 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:97 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:109 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/crc/CMakeLists.txt:150 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:19 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:61 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:115 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:132 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:169 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:191 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:223 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/debugging/CMakeLists.txt:285 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:18 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:34 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:54 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:75 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:96 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:113 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:133 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:151 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:174 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:199 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:224 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:250 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/flags/CMakeLists.txt:269 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/functional/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/functional/CMakeLists.txt:53 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/functional/CMakeLists.txt:81 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/hash/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/hash/CMakeLists.txt:106 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/hash/CMakeLists.txt:134 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:18 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:36 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:56 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:74 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:89 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:103 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:127 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:147 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:163 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:182 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:219 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:248 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:264 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:281 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:363 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:377 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:394 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:409 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:424 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:444 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:463 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:487 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:507 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:526 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:541 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:563 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:580 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:597 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:643 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/log/CMakeLists.txt:658 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/memory/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/meta/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/meta/CMakeLists.txt:45 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/numeric/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/numeric/CMakeLists.txt:44 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/numeric/CMakeLists.txt:79 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/numeric/CMakeLists.txt:89 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/profiling/CMakeLists.txt:15 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/profiling/CMakeLists.txt:40 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/profiling/CMakeLists.txt:67 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:35 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:70 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:161 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:199 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:214 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:517 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:531 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:547 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:561 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:583 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:639 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:657 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:672 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:689 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:705 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:719 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:739 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:757 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:775 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:792 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:810 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:827 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:847 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:864 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/random/CMakeLists.txt:1155 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/status/CMakeLists.txt:16 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/status/CMakeLists.txt:58 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:77 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:396 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:409 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:579 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:620 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:647 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:676 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:691 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:725 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:794 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:833 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/strings/CMakeLists.txt:866 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/synchronization/CMakeLists.txt:18 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/synchronization/CMakeLists.txt:37 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/synchronization/CMakeLists.txt:50 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/time/CMakeLists.txt:17 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/time/CMakeLists.txt:45 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/time/CMakeLists.txt:61 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:16 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:33 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:47 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:106 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:163 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:183 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:198 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:296 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/types/CMakeLists.txt:332 (absl_cc_library)
+
+
+CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
+  Force CXX_FLAGS flags to cxx_std_17
+Call Stack (most recent call first):
+  build/_deps/absl-src/absl/utility/CMakeLists.txt:17 (absl_cc_library)
+
+
+-- Fetching Abseil-cpp - fetched
+-- Fetching Protobuf
+--   Populating protobuf
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/protobuf-subbuild
+[100%] Built target protobuf-populate
+--   
+--   23.3.0
+-- Fetching Protobuf - fetched
+-- Fetching re2
+--   Populating re2
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/re2-subbuild
+[100%] Built target re2-populate
+-- Fetching re2 - fetched
+-- Fetching Eigen3
+--   Populating eigen3
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/eigen3-subbuild
+[100%] Built target eigen3-populate
+--   Performing Test COMPILER_SUPPORT_std=cpp03
+--   Performing Test COMPILER_SUPPORT_std=cpp03 - Success
+--   Standard libraries to link to explicitly: none
+--   Found unsuitable Qt version "5.15.3" from /usr/bin/qmake
+--   Qt4 not found, so disabling the mandelbrot and opengl demos
+--   Could NOT find CHOLMOD (missing: CHOLMOD_INCLUDES CHOLMOD_LIBRARIES) 
+--   Could NOT find UMFPACK (missing: UMFPACK_INCLUDES UMFPACK_LIBRARIES) 
+--   Could NOT find KLU (missing: KLU_INCLUDES KLU_LIBRARIES) 
+--   Could NOT find SuperLU (missing: SUPERLU_INCLUDES SUPERLU_LIBRARIES SUPERLU_VERSION_OK) (Required is at least version "4.0")
+--   A version of Pastix has been found but pastix_nompi.h does not exist in the include directory. Because Eigen tests require a version without MPI, we disable the Pastix backend.
+--   
+--   Configured Eigen 3.4.0
+--   
+--   Available targets (use: make TARGET):
+--   ---------+--------------------------------------------------------------
+--   Target   |   Description
+--   ---------+--------------------------------------------------------------
+--   install  | Install Eigen. Headers will be installed to:
+--            |     <CMAKE_INSTALL_PREFIX>/<INCLUDE_INSTALL_DIR>
+--            |   Using the following values:
+--            |     CMAKE_INSTALL_PREFIX: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
+--            |     INCLUDE_INSTALL_DIR:  include/eigen3
+--            |   Change the install location of Eigen headers using:
+--            |     cmake . -DCMAKE_INSTALL_PREFIX=yourprefix
+--            |   Or:
+--            |     cmake . -DINCLUDE_INSTALL_DIR=yourdir
+--   doc      | Generate the API documentation, requires Doxygen & LaTeX
+--   blas     | Build BLAS library (not the same thing as Eigen)
+--   uninstall| Remove files installed by the install target
+--   ---------+--------------------------------------------------------------
+--   
+-- Fetching Eigen3 - fetched
+-- Fetching googletest
+--   Populating googletest
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/googletest-subbuild
+[100%] Built target googletest-populate
+-- Fetching googletest - fetched
+-- Found long size: 8
+-- Found long long size: 8
+-- Found int64_t size: 8
+-- Found unsigned long size: 8
+-- Found unsigned long long size: 8
+-- Found uint64_t size: 8
+-- Found int * size: 8
+-- Adding proto path: $<BUILD_INTERFACE:/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/protobuf-src/src>
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/knapsack.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/knapsack.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/simple_knapsack_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/simple_knapsack_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_linear_sum_assignment.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_linear_sum_assignment.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_min_flow.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_min_flow.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/balance_min_flow.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/balance_min_flow.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_max_flow_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_max_flow_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_min_cost_flow_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_min_cost_flow_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/glop/samples/simple_glop_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/glop/samples/simple_glop_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/cp_is_fun_cp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/cp_is_fun_cp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/minimal_jobshop_cp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/minimal_jobshop_cp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nqueens_cp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nqueens_cp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nurses_cp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nurses_cp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/rabbits_and_pheasants_cp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/rabbits_and_pheasants_cp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_cp_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_cp_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_ls_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_ls_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_routing_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_routing_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_circuit_board.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_circuit_board.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities_routes.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities_routes.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_distance_matrix.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_distance_matrix.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_breaks.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_breaks.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_capacity.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_capacity.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_drop_nodes.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_drop_nodes.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_global_span.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_global_span.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_initial_routes.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_initial_routes.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_fifo.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_fifo.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_lifo.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_lifo.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_resources.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_resources.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_routes.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_routes.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_solution_callback.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_solution_callback.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_starts_ends.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_starts_ends.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_time_windows.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_time_windows.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_with_time_limit.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_with_time_limit.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrptw_store_solution_data.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrptw_store_solution_data.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_groups_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_groups_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_task_sizes_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_task_sizes_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_teams_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_teams_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/basic_example.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/basic_example.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/bin_packing_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/bin_packing_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/integer_programming_example.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/integer_programming_example.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/linear_programming_example.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/linear_programming_example.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/mip_var_array.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/mip_var_array.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/multiple_knapsack_mip.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/multiple_knapsack_mip.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_lp_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_lp_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_mip_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_mip_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/stigler_diet.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/stigler_diet.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/pdlp/samples/simple_pdlp_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/pdlp/samples/simple_pdlp_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_groups_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_groups_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_task_sizes_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_task_sizes_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_teams_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_teams_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assumptions_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assumptions_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/binpacking_problem_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/binpacking_problem_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/bool_or_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/bool_or_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/channeling_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/channeling_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/copy_model_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/copy_model_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_is_fun_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_is_fun_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_sat_example.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_sat_example.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/earliness_tardiness_cost_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/earliness_tardiness_cost_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/interval_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/interval_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/literal_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/literal_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/minimal_jobshop_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/minimal_jobshop_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/multiple_knapsack_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/multiple_knapsack_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/no_overlap_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/no_overlap_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/non_linear_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/non_linear_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nqueens_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nqueens_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nurses_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nurses_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/optional_interval_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/optional_interval_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/rabbits_and_pheasants_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/rabbits_and_pheasants_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/ranking_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/ranking_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/reified_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/reified_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/schedule_requests_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/schedule_requests_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/search_for_all_solutions_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/search_for_all_solutions_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/simple_sat_program.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/simple_sat_program.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solution_hinting_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solution_hinting_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_and_print_intermediate_solutions_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_and_print_intermediate_solutions_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_with_time_limit_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_with_time_limit_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/step_function_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/step_function_sample_sat.cc: ...DONE
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/stop_after_n_solutions_sample_sat.cc: ...
+-- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/stop_after_n_solutions_sample_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/constraint_programming_cp.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/constraint_programming_cp.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/costas_array_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/costas_array_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cryptarithm_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cryptarithm_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrp_disjoint_tw.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrp_disjoint_tw.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_resources.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_resources.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_stop_times_and_resources.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_stop_times_and_resources.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/flow_api.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/flow_api.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/golomb_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/golomb_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/integer_programming.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/integer_programming.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_assignment_api.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_assignment_api.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_programming.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_programming.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_solver_protocol_buffers.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_solver_protocol_buffers.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_sequence_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_sequence_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_square_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_square_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/max_flow.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/max_flow.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/min_cost_flow.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/min_cost_flow.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/nqueens.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/nqueens.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/qap_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/qap_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/random_tsp.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/random_tsp.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/slitherlink_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/slitherlink_sat.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/uncapacitated_facility_location.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/uncapacitated_facility_location.cc: ...DONE
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/variable_intervals_sat.cc: ...
+-- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/variable_intervals_sat.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/bug_fz1.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/bug_fz1.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/cpp11_test.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/cpp11_test.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/forbidden_intervals_test.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/forbidden_intervals_test.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/init_test.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/init_test.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue1303.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue1303.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue173.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue173.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue57.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue57.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/lp_test.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/lp_test.cc: ...DONE
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/min_max_test.cc: ...
+-- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/min_max_test.cc: ...DONE
+-- Configuring done
+-- Generating done
+-- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build
+gmake: Makefile: No such file or directory
+gmake: *** No rule to make target 'Makefile'.  Stop.
+
+```
+
+### vvbandeira
+@idokoike, please file a GitHub Issue and fill out our form which includes you environment and OS, also include which steps did you take, e.g., did you run the DependencyInstaller.sh? If not, any reason why?
+

Build/4269.md

@@ -0,0 +1,52 @@
+# How to add new classes/structures to OpenROAD's schema?
+
+Tool: OpenDB
+
+Subcategory: Code generation issue
+
+## Conversation
+
+### fgaray
+Hello OpenRoad devs,
+
+I am following https://github.com/The-OpenROAD-Project/OpenROAD/discussions/3619 to implement a structure to share scan chain data between OpenROAD's components but I am blocked at an compile issue.
+
+See: https://github.com/fgaray/OpenROAD/tree/ctl_db, path src/odb/src/codeGenerator/schema/scan
+
+I am adding 3 new *.json files: dbScanInst.json dbScanPartition.json dbScanPin.json
+
+In dbScanPin.json I am defining an "union" of dbBTerm and dbITerm
+
+In dbScanPartition.json I am trying to use dbScanPin for my "start" and "stop" fields.
+
+
+I am running the ./generate script in src/odb/src/codeGenerator to generate the C++ code but I am getting the following error:
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/1619948/fc8774d8-b742-4407-86ef-e877d347f5d3)
+
+Looks like it is trying to use dbScanPin in the private dbScanPartition.h class, but if I change it to _dbScanPin in my  dbScanPartition.json, then it fails in the public class definition in db.h.
+
+Is there an step that I am missing or maybe some config?
+
+Thanks!
+
+
+### maliberty
+Use dbId to store references to other db objects
+```
+       "name": "start",
+-      "type": "dbScanPin"
++      "type": "dbId<dbScanPin>"
+     },
+     {
+       "name": "stop",
+-      "type": "dbScanPin"
++      "type": "dbId<dbScanPin>"
+     },
+```
+
+### fgaray
+I forgot to close this issue, but the answer was given by @maliberty .
+
+Writing the custom setter was the way to go when implementing this.
+

Build/4956.md

@@ -0,0 +1,67 @@
+# OpenROAD Build From Sources
+
+Subcategory: Compilation error
+
+## Conversation
+
+### sebinho
+Hello Guys,
+
+I am using ArchLinux and I have been using OpenROAD from an install package from the AUR. 
+This install does not seem to work anymore (it was working on my setup a couple of weeks ago).
+
+So I am trying to build from sources but I get the same errors as I get with the AUR package:
+```
+[ 74%] Building CXX object src/gui/CMakeFiles/gui.dir/src/scriptWidget.cpp.o
+In file included from /home/zed/repos/OpenROAD/src/gui/src/tclCmdInputWidget.h:50,
+                 from /home/zed/repos/OpenROAD/src/gui/src/scriptWidget.cpp:49:
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h: In function ‘int SWIG_Tcl_GetArgs(Tcl_Interp*, int, Tcl_Obj* const*, const char*, ...)’:
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:11: error: ‘Tcl_Size’ was not declared in this scope; did you mean ‘Tcl_Time’?
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |           ^~~~~~~~
+      |           Tcl_Time
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:21: error: ‘vlptr’ was not declared in this scope; did you mean ‘vptr’?
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |                     ^~~~~
+      |                     vptr
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:40: error: expected primary-expression before ‘)’ token
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |                                        ^
+make[2]: *** [src/gui/CMakeFiles/gui.dir/build.make:226: src/gui/CMakeFiles/gui.dir/src/scriptWidget.cpp.o] Error 1
+make[2]: *** Waiting for unfinished jobs....
+[ 74%] Building CXX object src/rcx/src/CMakeFiles/rcxUnitTest.dir/__/test/ext2dBoxTest.cpp.o
+In file included from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/UVLADIE3JM/../../../../../src/gui/src/tclCmdInputWidget.h:50,
+                 from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/UVLADIE3JM/moc_tclCmdInputWidget.cpp:10,
+                 from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/mocs_compilation.cpp:23:
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h: In function ‘int SWIG_Tcl_GetArgs(Tcl_Interp*, int, Tcl_Obj* const*, const char*, ...)’:
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:11: error: ‘Tcl_Size’ was not declared in this scope; did you mean ‘Tcl_Time’?
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |           ^~~~~~~~
+      |           Tcl_Time
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:21: error: ‘vlptr’ was not declared in this scope; did you mean ‘vptr’?
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |                     ^~~~~
+      |                     vptr
+/home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:40: error: expected primary-expression before ‘)’ token
+ 1623 |           Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
+      |                                        ^
+[ 74%] Linking CXX executable dpl_test
+```
+
+Seems to be something related to Swig with TCL. Does anybody know what the problem is?
+
+Thanks for your help
+
+
+
+### maliberty
+What version of TCL and swig do you have installed?
+
+### maliberty
+Perhaps something is different in 4.2.1 as with 4.1.0 I don't see any used of Tcl_Size in tclSwig.h.  Is it possible for you to downgrade?
+
+### stefanottili
+Does anybody know how to downgrade swig on MacOS M1 homebrew ?
+The current SWIG Version 4.2.1 causes the same error here.
+Can be worked around by commenting out the two offending lines, they seem to be in an error path ...  
+

Build/5101.md

@@ -0,0 +1,31 @@
+# OpenROAD build with recent versions of FMT and SPDLOG
+
+Subcategory: Dependency compatibility issues
+
+## Conversation
+
+### sebinho
+I am not sure where to put this, but I had lots of issues lately building OpenROAD on ArchLinux and I thought this might help other people.
+The issues I had seem to be related to more recent versions of spdlog and fmt packages.
+Dowgrading fmt to 8.1.1-2 and spdlog to 1.13.0 solves the issues (latest versions are 10.2.0-1 and 1.14.1-1).
+
+The issues were as follows during the build (one example, others are similar):
+
+```
+/usr/include/fmt/core.h:1600:63: error: ‘fmt::v10::detail::type_is_unformattable_for<const dpl::TypedCoordinate<dpl::GridYType>, char> _’ has incomplete type
+ 1600 |     type_is_unformattable_for<T, typename Context::char_type> _;
+      |                                                               ^
+/usr/include/fmt/core.h:1604:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter<T> specialization: https://fmt.dev/latest/api.html#udt
+ 1604 |       formattable,
+      |       ^~~~~~~~~~~
+/usr/include/fmt/core.h:1604:7: note: ‘formattable’ evaluates to false
+```
+
+The better way for me to solve my issue (instead of downgrading packages) was to build OpenROAD with the following flag during `cmake`: `-DSPDLOG_FMT_EXTERNAL=OFF`
+
+### rovinski
+You might want to take a look at the dependency installer because this issue is known. It may not have support for Arch but you can look at comments for other distros for notes like this.
+
+### maliberty
+Please see my comment about FMT_DEPRECATED_OSTREAM  in https://github.com/The-OpenROAD-Project/OpenROAD/pull/2696
+

Configuration/2442.md

@@ -0,0 +1,20 @@
+# Unable to find image 'openroad/flow-scripts:latest' locally
+
+Subcategory: Docker setup issue
+
+## Conversation
+
+### heaton56
+After install, trying to run the docker I get the following. ny ideas?
+
+Unable to find image 'openroad/flow-scripts:latest' locally
+docker: Error response from daemon: pull access denied for openroad/flow-scripts, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
+
+### maliberty
+How did you 'install' it?  What command did you run that gave this message?
+
+### heaton56
+Thanks for you response, but I decided to do a local install of OpenROAD-flow-scripts instead, since I would have a learning curve with docker. 
+
+
+

Configuration/3350.md

@@ -0,0 +1,41 @@
+# Which distros to support
+
+Subcategory: Environment setup
+
+## Conversation
+
+### maliberty
+Currently OR CI is built with
+* Local centos7 gcc8
+* Local centos7 gcc8 without GUI
+* Docker centos7 gcc8
+* Docker ubuntu20.04 gcc9
+
+PRs additionally have GH actions that test:
+* macOS (x86)
+* c++20 (using clang-16)
+
+Centos7 is getting quite dated and I think it is time to replace it with a more modern distro.  #3344 shows an example problem where qt5charts is not available in this older distro.  I think Ubuntu 22 or Debian 11 are good contenders.
+
+I'd like community input as to what distro others are using with OR to help guide our choice.  @antonblanchard @gadfort @QuantamHD @rovinski @msaligane @oharboe @donn @nayiri-k
+
+The default compiler version would be updated to match the distro default.
+
+FYI @vvbandeira @tspyrou 
+
+### QuantamHD
+Google is on Debian test called [Glinux](https://en.wikipedia.org/wiki/GLinux). Ubuntu 22 or Debian 11 seem like reasonable choices to me.
+
+But we use bazel to build everything from source so the biggest issue for me is if we start requiring very new versions of widely used libraries like Boost, because then I have to upgrade all of Google to use that version of software which can be a big pain.
+
+Google has a one version policy for any piece of software in the universe, and it's all stored in a monorepo.
+
+### donn
+I use Nix as a build system, so as long as the CMakeFiles are generic enough to compile on both macOS, Ubuntu and CentOS I have no issues with the specific versions of the operating system.
+
+### rovinski
+CentOS 7 is EOL on 2024-06-30. I know of machines that are still running it, so maybe it would be a good idea to hold off removing support until then.
+
+### olofk
+As a data point, I wanted to mention that I just got it running on Gentoo, depending only on system packages except for or-tools
+

Configuration/3943.md

@@ -0,0 +1,35 @@
+# How to develop the " setRC.tcl "  file from a captable for a foreign PDK ?
+
+Tool: Parasitics Extraction
+
+Subcategory: Setting up foreign PDK
+
+## Conversation
+
+### faisaladilquadery
+I have a foreign PDK which I want to invoke in openroad. But for that I need to develop the setRC.tcl file. How do I accurately input the resistance and capacitance for the setRC.tcl file . 
+
+N.B : I have a captable for the pdk
+I can also generate a spef file from Innovus for the PDK
+
+### maliberty
+@vvbandeira @luarss do we have any documentation for correlateRC ?
+
+Note that if you LEF res & cap has values you can use those without a setRC to get started.
+
+### vvbandeira
+@faisaladilquadery 
+We have a section on the `setRC.tcl` file configuration in our platform bring-up documentation.
+https://openroad-flow-scripts.readthedocs.io/en/latest/contrib/PlatformBringUp.html#setrc-configuration
+
+### faisaladilquadery
+Thankyou! @maliberty @vvbandeira . I have used the lef file in replacement of the setRC.tcl file . But I am getting **net delay** mismatch between the same path with the same cells for Innovus and OpenRoad. Any Idea why ?
+
+### faisaladilquadery
+Thankyou @maliberty I have used the the RCX flow you  mentioned to generate a rc tech file for my pdk and used the tech file to generate a spef in ORFS to obtain a more accurate RC.
+
+### b224hisl
+> set_wire_rc is used to set a default layer to use when doing placement based parasitic estimation. There is no meaning to multiple layers here as there would be no way to divide up the estimate meaningfully.
+
+So I'm confused why it needs to set jsut one layer, do you mean only placement based parasitic estimation is related to `set_wire_rc` ? If there' s no way to divide up the estimate meaningfully, the layer can be set randomly?
+

Configuration/4289.md

@@ -0,0 +1,31 @@
+# Disable LEF Warning Messages
+
+Tool: OpenDB
+
+Subcategory: Warnings and messages
+
+## Conversation
+
+### abaababa
+Hi all,
+
+I am trying to load custom lef/lib files for pnr, and my lef files contain some properties unsupported by openroad. I got too much warning messages from this and the unsupported properties didn't have effect on my pnr results. Is there any way to disable the LEF warning messages temporarily? I checked the documents but failed to find an option that can turn off the warnings. Sorry if I missed it from the documents.
+
+Thanks in advance!
+
+
+
+### maliberty
+There is no method to do that currently.  No single message will print more than 1k times.
+
+### luarss
+@maliberty  Correct me if I am wrong, but doesn't Tcl function `suppress_message` do this? 
+
+Edit: i guess there's no function that achieves full suppression for all warnings, what OP requested
+
+https://github.com/The-OpenROAD-Project/OpenROAD/blob/28892de3bef1af52f3371d547f752acf0af20021/test/helpers.tcl#L203
+
+Corresponding source:
+https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/utl/src/Logger.cpp
+
+

Configuration/4515.md

@@ -0,0 +1,23 @@
+# How do I avoid cells rotation in placement?
+
+Tool: Detailed Placement
+
+Subcategory: Cell placement rules
+
+## Conversation
+
+### OuDret
+I need a cell that does not rotate in both global and detailed placement. Is there any way to achieve it? I did not find any parameter.  
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/74424277/9d1b472c-dac6-4458-a3f6-f045e42abcfc)
+
+Thanks
+
+
+
+### maliberty
+If it is a standard cell the LEF for the cell gives its symmetry.
+
+### maliberty
+As this isn't a usual use case it has been lower priority.  The simplest thing might be to just delete the rows that represent Y symmetry if you want to avoid such for your experiments.
+

Configuration/5065.md

@@ -0,0 +1,155 @@
+# howo to run openroad by reading an existing DEF file
+
+Tool: OpenDB
+
+Subcategory: Initialization from existing DEF
+
+## Conversation
+
+### bittnada
+Hello
+I have a DEF file in which row, track, components, and pins are written.
+The position of the cells are on the step of global placement, obtained by using another method.
+Now, I want to finish the rest of the procedures by modifying "test/flow.tcl" file.
+I just skipped the steps of pin placement and global placement and  added "read_def [my_def_fiel}'", but it did not work.
+I will appreciate if anyone let me know how to solve this problem.
+Thanks,
+
+
+
+### maliberty
+What happened when it "did not work"?  Its not much to go on.
+
+### bittnada
+
+Sorry for my delayed response.
+
+I've just conducted a test using gcd_nangate45.tcl, and I've created my own DEF file containing rows, tracks, pins, nets, and components. I performed a simple test by modifying a flow.tcl script to skip buffer insertion, IO placement, Macro Placement, tap cell insertion, power distribution, and global placement, and then adding "read_def".
+
+After running gcd_nangate45.tcl, I received the following output:
+
+====================================================================================
+OpenROAD v2.0-13652-g6fc686431 
+Features included (+) or not (-): +Charts +GPU +GUI +Python
+This program is licensed under the BSD-3 license. See the LICENSE file for details.
+Components of this program may be licensed under more restrictive licenses which must be honored.
+[INFO ODB-0227] LEF file: Nangate45/Nangate45_tech.lef, created 22 layers, 27 vias
+[INFO ODB-0227] LEF file: Nangate45/Nangate45_stdcell.lef, created 135 library cells
+[WARNING STA-0441] set_input_delay relative to a clock defined on the same port/pin not allowed.
+[INFO IFP-0001] Added 57 rows of 422 site FreePDK45_38x28_10R_NP_162NW_34O.
+[INFO ORD-0048] Loading an additional DEF.
+Error: Chip already exists
+[INFO RSZ-0058] Using max wire length 693um.
+[INFO RSZ-0039] Resized 41 instances.
+Placement Analysis
+---------------------------------
+total displacement      17739.5 u
+average displacement       49.0 u
+max displacement           62.9 u
+original HPWL             280.4 u
+legalized HPWL           9839.7 u
+delta HPWL                 3410 %
+
+worst slack 0.105
+worst slack -0.011
+tns -0.011
+[INFO CTS-0050] Root buffer is BUF_X4.
+[INFO CTS-0051] Sink buffer is BUF_X4.
+[INFO CTS-0052] The following clock buffers will be used for CTS:
+                    BUF_X4
+[INFO CTS-0049] Characterization buffer is BUF_X4.
+[INFO CTS-0007] Net "clk" found for clock "core_clock".
+[WARNING CTS-0041] Net "clk" has 0 sinks. Skipping...
+[WARNING CTS-0083] No clock nets have been found.
+[INFO CTS-0008] TritonCTS found 0 clock nets.
+[WARNING CTS-0082] No valid clock nets in the design.
+[INFO RSZ-0058] Using max wire length 693um.
+Placement Analysis
+---------------------------------
+total displacement          0.0 u
+average displacement        0.0 u
+max displacement            0.0 u
+original HPWL            9839.7 u
+legalized HPWL           9839.7 u
+delta HPWL                    0 %
+
+[INFO RSZ-0094] Found 1 endpoints with setup violations.
+[WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
+[WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
+[WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
+[WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
+[INFO RSZ-0041] Resized 5 instances.
+[INFO RSZ-0043] Swapped pins on 2 instances.
+[INFO RSZ-0033] No hold violations found.
+worst slack 0.106
+worst slack 0.000
+tns 0.000
+Placement Analysis
+---------------------------------
+total displacement         91.3 u
+average displacement        0.3 u
+max displacement            6.4 u
+original HPWL            9840.8 u
+legalized HPWL           9925.0 u
+delta HPWL                    1 %
+
+[INFO DRT-0149] Reading tech and libs.
+
+Units:                2000
+Number of layers:     21
+Number of macros:     135
+Number of vias:       27
+Number of viarulegen: 19
+
+Signal 11 received
+Stack trace:
+ 0# 0x0000564758181A44 in /mnt/work/OpenROAD/bin/bin/openroad
+ 1# 0x00007F4028F54F10 in /lib/x86_64-linux-gnu/libc.so.6
+ 2# odb::dbTechVia::getTopLayer() in /mnt/work/OpenROAD/bin/bin/openroad
+ 3# odb::dbWireEncoder::addTechVia(odb::dbTechVia*) in /mnt/work/OpenROAD/bin/bin/openroad
+ 4# drt::TritonRoute::stackVias(odb::dbBTerm*, int, int, bool) in /mnt/work/OpenROAD/bin/bin/openroad
+ 5# drt::TritonRoute::processBTermsAboveTopLayer(bool) in /mnt/work/OpenROAD/bin/bin/openroad
+ 6# drt::TritonRoute::initDesign() in /mnt/work/OpenROAD/bin/bin/openroad
+ 7# drt::TritonRoute::pinAccess(std::vector<odb::dbInst*, std::allocator<odb::dbInst*> > const&) in /mnt/work/OpenROAD/bin/bin/openroad
+ 8# pin_access_cmd(char const*, char const*, char const*, int, int) in /mnt/work/OpenROAD/bin/bin/openroad
+ 9# 0x00005647589E491B in /mnt/work/OpenROAD/bin/bin/openroad
+10# TclNRRunCallbacks in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
+11# 0x00007F402E79BFBA in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
+12# Tcl_EvalEx in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
+13# Tcl_Eval in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
+14# gui::TclCmdInputWidget::executeCommand(QString const&, bool, bool) in /mnt/work/OpenROAD/bin/bin/openroad
+15# gui::CmdInputWidget::handleEnterKeyPress(QKeyEvent*) in /mnt/work/OpenROAD/bin/bin/openroad
+16# gui::TclCmdInputWidget::keyPressEvent(QKeyEvent*) in /mnt/work/OpenROAD/bin/bin/openroad
+17# QWidget::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+18# QFrame::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+19# QAbstractScrollArea::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+20# QPlainTextEdit::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+21# QApplicationPrivate::notify_helper(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+22# QApplication::notify(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+23# QCoreApplication::notifyInternal2(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
+24# 0x00007F402B1357B5 in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+25# QApplicationPrivate::notify_helper(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+26# QApplication::notify(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+27# QCoreApplication::notifyInternal2(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
+28# QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
+29# QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
+30# QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
+31# 0x00007F4022595260 in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
+32# g_main_context_dispatch in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+33# 0x00007F402783C770 in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+34# g_main_context_iteration in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+35# QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
+36# QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
+37# QCoreApplication::exec() in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
+38# gui::startGui(int&, char**, Tcl_Interp*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) in /mnt/work/OpenROAD/bin/bin/openroad
+39# ord::tclAppInit(Tcl_Interp*) in /mnt/work/OpenROAD/bin/bin/openroad
+40# Tcl_MainEx in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
+41# main in /mnt/work/OpenROAD/bin/bin/openroad
+42# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
+43# _start in /mnt/work/OpenROAD/bin/bin/openroad
+================================================================================================
+
+I also examined the source codes and realized that the testing approach I employed did not yield the desired results. However, I am unsure about how to proceed from the step after global placement by reading the DEF file.
+
+Thanks.
+

Configuration/5199.md

@@ -0,0 +1,24 @@
+# Non-rectilinear core area
+
+Tool: Initialize Floorplan
+
+Subcategory: Floorplan customization
+
+## Conversation
+
+### Blebowski
+Hello,
+
+is it possible to somehow specify core-area that is non-rectilinear (e.g. as a group of polygons surrounding concave shape) ?
+
+I understand that if doing "digital on top" FP where all the analog is a digital macro, this does not make sense. However, it may be usefull in case where "analog-on-top" is done, and digital may have some weird shape and is eventually placed as hard GDSII macro into analog-on-top design.
+
+
+
+### maliberty
+The simplest would be to make a rectangular block and add placement and routing blockages for the disallowed area
+
+### Blebowski
+Thanks. Can I then do the `add_pdn_ring` around just the cut area (e.g. L-shape pdn-ring) ?  Or is there some other trick how
+to achieve this ?
+

Configuration/5213.md

@@ -0,0 +1,66 @@
+# Running a simple combinatorial design
+
+Tool: OpenDB
+
+Subcategory: Module name mismatch
+
+## Conversation
+
+### Dandy201
+Hi all, I'm new to using ORFS and tried some tutorials from https://github.com/The-OpenROAD-Project/micro2022tutorial. 
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/8a6e4ccd-503a-4751-8ead-8c1c5d209890)
+
+Completing exercise 5 got this simple output:
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/63ead36e-c51b-456b-9526-819d76f8a209).
+
+From this, I'm trying to make a simple combinational circuit. Running make DESIGN_CONFIG=../../half_Adder/config.mk, it always ends at this error:
+
+7. Executing Verilog-2005 frontend: /home/dan/Desktop/Work/vlsi/tools/OpenROAD-flow-scripts/flow/platforms/asap7/yoSys/cells_clkgate_R.v
+Using ABC speed script.
+[FLOW] Extracting clock period from SDC file: ./results/asap7/halfAdder/base/clock_period.txt
+[FLOW] Setting clock period to 5
+8. Executing SYNTH pass.
+8.1. Executing HIERARCHY pass (managing design hierarchy).
+**ERROR: TCL interpreter returned an error: Yosys command produced an error
+Command exited with non-zero status 1
+Elapsed time: 0:00.59[h:]min:sec. CPU time: user 0.56 sys 0.02 (99%). Peak memory: 72508KB.
+make[1]: *** [Makefile:496: do-yosys] Error 1
+make: *** [Makefile:499: results/asap7/halfAdder/base/1_1_yosys.v] Error 2.**
+
+Config file
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/324abeb8-c78c-42a6-906f-811f9c4134b6)
+
+Constraint file
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/c305c964-35a7-4fae-b038-7cbb9539f98d)
+
+Verilog file
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/fe9cc773-67be-4235-a4b5-b66b06dee795)
+
+
+
+
+
+### maliberty
+Please package this as a standalone test case and attach it.  Reproducing it from screen shots is inefficient.
+
+### Dandy201
+[try.zip](https://github.com/user-attachments/files/15751707/try.zip)
+
+Here's the  zip file along with the command : make DESIGN_CONFIG=../../try/config.mk
+
+
+### mi-and-core
+(1) change module name from 'half_adder' to 'halfAdder'
+
+
+### maliberty
+In the config.mk
+```
+export DESIGN_NAME = halfAdder
+```
+while in halfAdder.v:
+```
+module half_adder(
+```
+These names need to match.
+

Documentation/4495.md

@@ -0,0 +1,27 @@
+# pad_left/right units for GPL and repair_clock_inverters description
+
+Tool: Global Placement
+
+Subcategory: Missing information
+
+## Conversation
+
+### lustefan97
+
+
+I looked in OpenROAD documentation for Global Placement and Gate Resizer to get more detail about the units of the pad_left/right parameters of the `global_placement` command [(GPL)](https://github.com/The-OpenROAD-Project/OpenROAD/tree/master/src/gpl) and the use/behavior of `repair_clock_inverters` [(RSZ).](https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/rsz/README.md) 
+
+Both the variables units description is missing (while present for DPL (site count units), but since the two tools are different I don't want to assume it is the same for both) in GPL, and there is no description concerning `repair_clock_inverters` use case or behavior description (like there would be for `repair_timing` or `repair_design`.
+
+What are the units of pad_left/right, and what does `repair_clock_inverters` do/how to use it ?
+
+### maliberty
+The units are sites from the LEF.
+
+repair_clock_inverters is useful when you have an inverter in the clock tree that would split the tree.  It clones the inverter so you have one per flop instead.
+
+### maliberty
+before CTS see https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/181e9133776117ea1b9f74dbacbfdaadff8c331b/flow/scripts/cts.tcl#L7
+
+You might benefit from investigating how ORFS works
+

Documentation/5312.md

@@ -0,0 +1,34 @@
+# How to query odb database
+
+Tool: OpenDB
+
+Subcategory: Incomplete documentation
+
+## Conversation
+
+### titan73
+I want to directly query odb database. How can I do that? There is no command for that.
+I found some ord::xxx commands by searching the net but there is no proper documentation with all commands.
+
+### titan73
+also found odb::xxx. No documentation either.
+Most functions required a self argument.
+Tested "::odb::dbBlock_getPowerDomains [::odb::dbBlock]" to get power domains but it crashes.
+
+### titan73
+I got to something using orf and odb to get the created power domains:
+
+foreach pd [::odb::dbBlock_getPowerDomains [::ord::get_db_block]] {
+    puts "[::odb::dbPowerDomain_getName $pd]"
+}
+
+I think I get the idea. A pity it's not documented.
+
+
+### maliberty
+We use swig on https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/odb/include/odb/db.h so the APIs and comments there should be a guide.  If you have specific questions please ask.
+
+### titan73
+Ok thanks. It helps. Although not all methods have comments.  dbPowerDomain for instance.
+How does int& is supposed to be mapped in tcl? Ex: bool getArea(int& x1, int& y1, int& x2, int& y2);
+

FeatureRequest/1871.md

@@ -0,0 +1,23 @@
+# Support for MEOL layer?
+
+Tool: OpenDB
+
+Subcategory: Add MEOL layer support
+
+## Conversation
+
+### GuzTech
+Hello everyone!
+
+I'm in the process of bringing up a new platform which is going well. I am running into a problem with a local interconnect layer which is specified as a `MASTERSLICE` with `LEF58_TYPE` = `MEOL`, so it is not specified as a `ROUTING` layer as is the case with the sky130 PDK. OpenDB complains that there is a parse mismatch for this `lil` layer.
+
+If I add this `lil` layer as a routing layer to `make_tracks.tcl` then OpenDB complains that it is not a routing layer. If I don't add `lil` as a routing layer, then TritonRoute gives an error that it cannot find layer `lil` for viarule that connects `lil` to the first metal layer.
+
+Did anyone else run into a similar problem? If so, how did you solve it?
+
+### maliberty
+Please include the odb message.  You should not add tracks if it is not a routing layer.
+
+### maliberty
+We need to add support for MEOL.  You can workaround it my making it a masterslice layer temporarily.
+

FeatureRequest/2784.md

@@ -0,0 +1,108 @@
+# New DFT Tool: Starting with scan replace
+
+Tool: Design for Test
+
+Subcategory: New tool addition
+
+## Conversation
+
+### fgaray
+Hello OpenROAD devs,
+
+I am planning on contributing a new tool (following  https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/docs/contrib/DeveloperGuide.md, I will call this "dft") for DFT insertion into OpenROAD and I would like to discuss the user facing API.
+
+# User facing API
+
+I think we should create two new main commands for DFT: preview_dft and insert_dft:
+
+* preview_dft: will show a summary of what scan chains are we going to create (after scan architect) but will not apply any changes to the design. This is an immutable command and will not perform any modifications to the design or database. This is useful for debugging proposes and to help users to iterate any DFT option that could change the creation of the scan chains.
+* insert_dft: will run again from scratch the immutable part of preview_dft, including scan architect and perform scan stitching. The result of insert_dft should be the same that the one presented by preview_dft but applied to the design.
+
+I would say that it is better to configure the DFT compiler with commands like "set_dft_*" instead of receiving any argument in "preview_dft" or "insert_dft". For example: set_dft_no_scan (for cells that we don't want to scan replace), set_dft_chain_count (for the number of scan chains to be created) or set_dft_clock_mix (if we want or not to mix clock domains).
+
+Now, I am not sure if this is going to be something you expect to see in the Python interface, this is a very TCL oriented API and I would like to see if you have any suggestion on doing this more programmatically for Python scripting (maybe this is totally fine as we can have a different API for Python?).
+
+# Where in the flow is DFT insertion going to be?
+
+![OpenROAD's flow](https://user-images.githubusercontent.com/1619948/213331834-76ea8bb9-a63b-4576-90ff-5e6eca6e5647.png)
+
+Looking into OpenROAD's flow, I think the best part to perform DFT insertion is between "Logic Synthesis" and "Floorplanning". That way we floorplanning will have all the info about DFT to perform optimizations in the design.
+
+Feel free to suggest something different here :).
+
+# What is the plan?
+
+For now, I will only be creating "insert_dft" and "set_no_scan" for scan replacement: I will replace sequential cells (excluding black boxes as we don't have support for [CTLs](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=966626) yet!) in the design with scan equivalents if they are available and nothing more inside insert_dft. I will keep of of the scope adding scan muxes or any other kind of scan stitching as this is my first approach to OpenROAD.
+
+Please, let me know if there is something I should be aware of or anything related to this idea or the user interface.
+
+Thanks!,
+Felipe
+
+
+### maliberty
+I think it is best to do scan chain after global placement.  You want to put the ff in the best placement for timing and only then construct the chain ordering based on neighbors.  
+
+It would be helpful to know what commands you intend to implement to define the chains.  A small complete example would clarify the use model.
+
+For python API please see the discussion in https://github.com/The-OpenROAD-Project/OpenROAD/discussions/2745
+
+### maliberty
+@rovinski @msaligane @louiic @Colin-Holehouse  any comments?
+
+### rovinski
+Very cool! Always excited to see more functionality contributed 😃
+
+### maliberty
+Would you say more about scandef and how you intend to generate it?
+
+### maliberty
+Note that odb doesn't store any scan information from DEF today so you'll have to plan on enhancing it as part of this project.
+
+### maliberty
+In case its useful: http://vlsicad.eecs.umich.edu/BK/Slots/cache/vlsicad.ucsd.edu/GSRC/Bookshelf/Slots/ScanOpt/
+
+### fgaray
+Hey @maliberty , 
+
+I am trying to write a function to perform the scan replace and I need to find a scan equivalent cell in the DB.
+
+I am iterating over the libs in the odb::dbDatabase like this:
+
+```
+bool IsLibScanCell(odb::dbLib* lib) {
+  for (odb::dbMaster* master: lib->getMasters()) {
+    for (odb::dbMTerm* mterm: master->getMTerms()) {
+        std::cout << mterm->getSigType().getString() << std::endl;
+    }
+  }
+  return false;
+}
+```
+
+But looks like the enum of getSigType does not have enough information to see if a pin is scan_enable or scan_in. Is this something that I need to implement or is there another way to access this information inside the lib? I see that in sta/ there are some parsing to detect scan signals, but I do not see them being used in any place outside sta/.
+
+
+
+### fgaray
+For scan replace, I have a working demo where I collect the scan lib cells and then I try to iterate over the design's blocks applying "sta::dbNetwork" replaceCell, but I found that this and some methods in sta:: check before performing the replace if both cells are "equivalent" by counting the number of ports in each cell (See inDbInstSwapMasterBefore in dbSta/src/dbSta.cc ).
+
+This is not really true when you try to replace a cell with an scan equivalent because the scan one will have additional ports like scan in and scan enable.
+
+I was wondering if there is a function that I am missing that could help me with this kind of replace.
+
+If not, should I provide a new method for dbSta and odb that checks for functional equivalent ports instead of index/name based matching (See swapMaster in odb/src/db/dbInst.cpp) or roll one myself just for DFT? Would you prefer this method to be available in odb or maybe just complete change the way we do the replaceCell?
+
+Thanks!
+
+### fgaray
+Hi @maliberty,
+
+Do you know how to test if two ports/pins are functional equivalent?, I am trying to use sta::LibertyPort's function() and sta::FuncExpr::equiv() but looks like sta::LibertyPort's function() returns most of the time nullptr. I see that in odb/src/db/dbInst.cpp:1201, we test that mterms are equivalent by checking that the name of the ports is the same (line 1236). 
+
+I can work with that but I think my scan replace function will be more robust if I can check if the ports are functional equivalent.
+
+
+### fgaray
+Implemented basic DFT in #2900, #3079 and #3356
+

FeatureRequest/3331.md

@@ -0,0 +1,37 @@
+# Synthesis support
+
+Subcategory: Synthesis support
+
+## Conversation
+
+### Blebowski
+Hello, Is there any idea whether eventually OpenRoad would like to support also synthesis as part of the tool (instead of using Yosys externally) ?
+
+### maliberty
+There is no plan for that.  At most we would integrate yosys.  What motivates your question?
+
+### Blebowski
+Hi, @maliberty , several points:
+- Yosys does not support full System Verilog (AFAIK, only with proprietary parser). Nor it supports VHDL (only via GHDL yosys plugin, and  getting this to work is tricky)
+- Synthesis is mentioned several times in: https://github.com/The-OpenROAD-Project/OpenROAD/issues/1759
+1. Hard to get netlist that passes the timing
+2. Possible QoR gains
+
+- Generally, placement / routing aware synthesis reaches better results in lower geometries
+- Industry high-end goes this direction
+- Easier user interface (single database, simpler to pass information from synthesis to PnR)
+
+
+### Blebowski
+However,
+I need to note that I am not actively using nor developing OpenRoad. As for the usage, in company where I work, we use Synopsys for Synthesis and PnR tools due to stability, documentation, good performance and vast features available. We are looking forward for the day when we will be able to use open source.
+As for the development, I would really like to join, but I already have little time for the open-source work due to my daily job.
+
+### maliberty
+SV support is unrelated to OR and is being addressed in https://github.com/chipsalliance/Surelog.  The pain is mostly related to missing ASIC oriented features in yosys/abc (eg operator mapping).  
+
+In general its a large effort and would need dedicated resources to work on it.  There isn't enough bandwidth to make it a priority.  If you want to start addressing some of these concerns I'd be happy to discuss further.
+
+### maliberty
+OR has already integrated abc which handles the technology dependent operations.  Its less clear that there is a big advantage to the technology independent operations in yosys itself.  There is some work slowly progressing on remapping in OR using abc.
+

FeatureRequest/3359.md

@@ -0,0 +1,53 @@
+# Ideas for multithreaded rendering
+
+Tool: Graphical User Interface
+
+Subcategory: Performance enhancement
+
+## Conversation
+
+### rovinski
+I saw the conversation in #3330, #3342, #3348, etc. and started thinking about how the rendering time might be improved aside from not drawing objects that aren't useful.
+
+It seems that the rendering, for the most part, is embarrassingly parallel. In `LayoutViewer::drawInstanceOutlines()` for example (the most expensive layer measured in #3348), a function is applied to every instance in a vector to determine how / if it gets drawn, and then it makes a draw call.
+
+https://github.com/The-OpenROAD-Project/OpenROAD/blob/6920ac530b6959f742e75b7f55062b1642730b14/src/gui/src/layoutViewer.cpp#L2041-L2091
+
+This is essentially a [map reduce](https://en.wikipedia.org/wiki/MapReduce) paradigm which should be extremely parallel, except that Qt painter objects aren't thread safe. There was discussion in #3279 that the database is not "thread safe", but I think that was in the context of read/write operations and not read-only operations.
+
+Beyond that, each layer is independently but sequentially rendered:
+
+https://github.com/The-OpenROAD-Project/OpenROAD/blob/6920ac530b6959f742e75b7f55062b1642730b14/src/gui/src/layoutViewer.cpp#L2555-L2599
+
+There may or may not be ordering required on draw calls to these layers, I'm not sure.
+
+I looked at a few [Qt guides](https://doc.qt.io/qt-5/qtcore-threads-mandelbrot-example.html) and they all recommend separating computation from rendering in separate threads for better performance (and interactivity).
+
+I think some of these things were mentioned by @QuantamHD in #1930 but the PR itself seems to be unrelated (and abandoned).
+
+I have some interest in looking into this, but I wonder what the best approach would be for this? Qt has [QThread](https://doc.qt.io/qt-5/qthread.html) and [QThreadPool](https://doc.qt.io/qt-5/qthreadpool.html) for this exact purpose. There's also [QtConcurrent](https://doc.qt.io/qt-5/qtconcurrent.html) which may have some uses.
+
+In an ideal world, it seems like there should be a thread pool with `getThreadCount()-1` threads and the main thread. The main thread has a render queue which atomically pops the queue for draw calls and does nothing else until all worker threads yield. The worker threads can parallelize at the granularity of layer or instance/shape depending on what's optimal. But this could take a lot of refactoring, possibly be overkill, or possibly be difficult to tune the amount of threading correctly.
+
+An intermediate step could be to simply parallelize some of the heavy-weight tasks that block the GUI thread, such as using `std::transform(std::execution::par)` or `std::for_each(std::execution::par)` and separating the draw calls from the filtering. But also these functions don't seem to be well supported on old versions of GCC/Clang (it requires Intel `libtbb` and may error or just use a serial version if it isn't linked, but I think it also think it doesn't work on Apple silicon). Maybe using OpenMP would work?
+
+Any thoughts or opinions?
+@gadfort @maliberty @oharboe @QuantamHD 
+
+### oharboe
+After the recent performance improvement, the biggest performance problem currently for us, is that all intermediate zoom levels are rendered https://github.com/The-OpenROAD-Project/OpenROAD/issues/3278
+
+So if that could be fixed FIRST... :-)
+
+Afterwards, the suggestions that you propose sound wicked!
+
+It is true that Qt nor the database is thread safe, then on the other hand, this means that the GUI is single threaded, so I suppose that you are right that you can use as many or few threads as you like as long as Qt nor the database functions are non-the-wiser. Rendering should be especially amenable to this since it is a read only operation...
+
+Also, rendering doesn't have to be perfect.  I have been thinking that a draft could be rendered while zooming and then when the user stops giving input, more detail can be rendered.
+
+
+### maliberty
+@rovinski I've considered all these ideas but lack the time to implement them all.  Right now I'm looking at moving the rendering to a separate thread and making it interruptible.  The main challenge is figuring out how to trigger the right events at the right time to make Qt happy.  It is very particular that you can only paint in paintEvent.
+
+Assuming I can land this then it is more straightforward to split that worker thread into multiple threads.  KLayout works in a similar fashion where they render per layer in each thread and composite in the main thread.
+

FeatureRequest/3531.md

@@ -0,0 +1,17 @@
+# UPF support
+
+Tool: Unified Power Format (UPF)
+
+Subcategory: UPF support
+
+## Conversation
+
+### kareefardi
+Is https://github.com/The-OpenROAD-Project/OpenROAD/tree/master/src/upf a work in progress (it doesn't have documentation). If it is, is it planned to have it supported? 
+
+### maliberty
+UPF support is a work in progress.  The reader in upf/ works but the rest of the tool needs to support it.
+
+### maliberty
+I think the last remaining piece was pdn inserting the power switches.  @gadfort would you update on this?
+

FeatureRequest/3619.md

@@ -0,0 +1,110 @@
+# DFT: Storing scan chain information in odb
+
+Tool: Design for Test
+
+Subcategory: Scan chain representation
+
+## Conversation
+
+### fgaray
+Hello everyone,
+
+To support drawing scan chains in OpenROAD in the gui and CTL ([Core Test Language](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=966626)) parser/generator we need to make the scan info available in odb. Here I describe a DB schema to represent CTLs in odb.
+
+## Objective
+
+* Make scan chains available to the gui to be able to highlight scan structures and display information related to scan.
+* Provide a common source of true for other commands to query and find scan structures on the design.
+* Provide support for a future parser for CTLs files.
+
+## Out of scope
+
+* Parsing and writing a CTL file at this time.
+* Handling test patterns.
+
+## CTLs
+
+CTLs are files based on the [STIL standard](https://grouper.ieee.org/groups/1450/dot1/p1450.1-D14.pdf) that allow us to share information between DFT tools for optimizations and interoperability between different vendors. They describe the internal scan structures and they are useful too to share information between internal commands inside OpenROAD, like scan insertion and the GUI.
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/1619948/b513ec9c-4575-45c4-bac0-0401ab164da2)
+
+Source: CTL for Test Information of Digital ICs, Rohit Kapur
+
+**The schema described here is not a 1:1 map of a CTL file but should be enough to create one or to store the information coming from a CTL.**
+
+## dbScanChain
+
+* name: string
+* length: uint
+* cells: list\<dbInst\>
+* scanIn: dbScanPin
+* scanOut: dbScanPin
+* scanClock: dbScanPin
+* scanEnable: dbScanPin
+* testMode: string
+* partitions: list\<dbScanPartition\>
+* scanInsts: list\<dbScanInst\>
+
+## dbScanPin
+
+Wrapper to handle either dbBTerm or dbITerm:
+
+* bterm: dbBTerm
+* iterm: dbITerm
+
+## dbScanPartition
+
+* start: dbScanPin
+* stop: dbScanPin
+* name: string
+
+## dbScanInst
+
+* scanIn: dbScanPin
+* scanOut: dbScanPin
+* bits: uint
+* type: enum [OneBit, ShiftRegister, BlackBox]
+
+
+## Flow
+
+At the end of *insert_dft* we will be storing the scan chain information into odb using the created dbCTL object. The gui will be able to query this information and display it. dbScanChain will be attached to the dbBlock that contains the scan chains that are inside it.
+
+
+## Open Questions
+
+* Where can I add a new dbObject (dbCTL) to dbBlock? 
+* How can I represent maps (will std::map work?) string-> dbObject in the json db format?
+* I am creating a wrapper for dbBTerm and dbITerm for cases where the scan pins are not coming from the block, is there any way to handle this in the json db format? 
+
+
+
+### fgaray
+Hi @maliberty , who do you think is the right person to review this? Specially the open questions at the end.
+
+Thanks!
+
+### maliberty
+Scan chain is used in both CTL and in DEF.  Can dbScanChain accommodate both or do we need to consider having two classes?  If the later, how would you suggest naming them ?
+
+### maliberty
+Looking at DEF:
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/761514/6a7a39c4-e9b0-44e5-8beb-0fe450c7928d)
+
+It looks like the dbScanPartition needs a way to store MAXBITS.  
+
+Each element of the chain also has a BITS field which seems hard to represent here.  Perhaps we need a dbScanInst?
+
+How would you infer FLOATING or ORDERED from the design?
+
+### fgaray
+Hi @maliberty ,
+
+Do you think we are ready to start the implementation?
+
+Thanks!,
+Felipe
+
+### QuantamHD
+LGTM. Thanks for the contirbution @fgaray 
+

FeatureRequest/3788.md

@@ -0,0 +1,434 @@
+# Clock Tree Viewer and trying to get to the information in the tooltips
+
+Tool: Graphical User Interface
+
+Subcategory: Data visualization improvement
+
+## Conversation
+
+### oharboe
+The tooltips in the Clock Tree Viewer contain interesting information: which macro or flip flop has how much clock network latency.
+
+However, the tooltip information is hard to get to and it is not searchable.
+
+I mocked a text report that is printed when I click update...
+
+I think perhaps a better approach to this is to have a tcl utility procedure that navigates the clock tree and print out this information. Perhaps that is possible today, but I don't know how to...
+
+Change I used to mock the report below: https://github.com/Pinata-Consulting/OpenROAD/commit/17283788372d98cafc1e6bbd056f1074a1539bc6
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/1a874efa-2b66-41f2-b365-7990f3ed5399)
+
+
+### oharboe
+Mocking a heatmap of arrival times. I only have location information for the Elements. Got the idea here. https://www.eng.biu.ac.il/temanad/files/2017/02/Lecture-8-CTS.pdf
+
+```
+import re
+import matplotlib.pyplot as plt
+import numpy as np
+
+# Extracting data from the text
+text = """
+# Your log content goes here
+"""
+
+lines = text.strip().split('\n')
+filtered_lines = [line for line in lines if "ces" in line]
+
+# Finding the maximum indices for rows and columns
+max_row = max_col = 0
+data_dict = {}
+for line in filtered_lines:
+    match = re.search(r"ces_(\d+)_(\d+)/clock\s*Arrival:\s*(\d+\.\d+)", line)
+    if match:
+        row, col, value = map(int, map(float, match.groups()))
+        max_row = max(max_row, row)
+        max_col = max(max_col, col)
+        data_dict[(row, col)] = value
+
+# Constructing the data matrix
+data_matrix = np.zeros((max_row + 1, max_col + 1))
+for (row, col), value in data_dict.items():
+    data_matrix[row, col] = value
+
+# Plotting the heatmap
+plt.imshow(data_matrix, origin='upper', cmap='viridis', aspect='auto')
+plt.colorbar(label='Arrival (ps)')
+plt.title('Heatmap of Arrival Times')
+plt.xlabel('Column')
+plt.ylabel('Row')
+plt.show()
+```
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/aceb47d0-d673-461d-a0f0-e0b3df96a8d6)
+
+
+### oharboe
+Adding some 3d bling...
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/ad5b4839-f77e-4643-89d8-4426b4137f89)
+
+
+```
+# Sample data
+text = """
+[INFO GUI-0088] Register                                 _131_/CLK                                Arrival: 258.115 ps
+[INFO GUI-0088] Register                                 _132_/CLK                                Arrival: 257.882 ps
+[INFO GUI-0088] Register                                 _133_/CLK                                Arrival: 258.944 ps
+[INFO GUI-0088] Register                                 _134_/CLK                                Arrival: 258.636 ps
+[INFO GUI-0088] Register                                 _135_/CLK                                Arrival: 258.069 ps
+[INFO GUI-0088] Register                                 _137_/CLK                                Arrival: 257.527 ps
+[INFO GUI-0088] Register                                 _139_/CLK                                Arrival: 246.072 ps
+[INFO GUI-0088] Register                                 _143_/CLK                                Arrival: 245.541 ps
+[INFO GUI-0088] Register                                 _145_/CLK                                Arrival: 245.360 ps
+[INFO GUI-0088] Register                                 ces_0_7/clock                            Arrival: 232.150 ps
+[INFO GUI-0088] Register                                 ces_1_7/clock                            Arrival: 225.713 ps
+[INFO GUI-0088] Register                                 _136_/CLK                                Arrival: 250.476 ps
+[INFO GUI-0088] Register                                 _138_/CLK                                Arrival: 250.337 ps
+[INFO GUI-0088] Register                                 _140_/CLK                                Arrival: 246.845 ps
+[INFO GUI-0088] Register                                 _141_/CLK                                Arrival: 246.075 ps
+[INFO GUI-0088] Register                                 _142_/CLK                                Arrival: 246.461 ps
+[INFO GUI-0088] Register                                 _144_/CLK                                Arrival: 246.885 ps
+[INFO GUI-0088] Register                                 _146_/CLK                                Arrival: 245.560 ps
+[INFO GUI-0088] Register                                 ces_0_6/clock                            Arrival: 235.587 ps
+[INFO GUI-0088] Register                                 _147_/CLK                                Arrival: 239.633 ps
+[INFO GUI-0088] Register                                 _148_/CLK                                Arrival: 238.903 ps
+[INFO GUI-0088] Register                                 _149_/CLK                                Arrival: 239.580 ps
+[INFO GUI-0088] Register                                 _150_/CLK                                Arrival: 238.791 ps
+[INFO GUI-0088] Register                                 _151_/CLK                                Arrival: 239.418 ps
+[INFO GUI-0088] Register                                 _152_/CLK                                Arrival: 239.304 ps
+[INFO GUI-0088] Register                                 _153_/CLK                                Arrival: 238.755 ps
+[INFO GUI-0088] Register                                 _154_/CLK                                Arrival: 238.495 ps
+[INFO GUI-0088] Register                                 _155_/CLK                                Arrival: 250.283 ps
+[INFO GUI-0088] Register                                 _156_/CLK                                Arrival: 250.061 ps
+[INFO GUI-0088] Register                                 _157_/CLK                                Arrival: 250.546 ps
+[INFO GUI-0088] Register                                 _158_/CLK                                Arrival: 250.032 ps
+[INFO GUI-0088] Register                                 _159_/CLK                                Arrival: 250.760 ps
+[INFO GUI-0088] Register                                 _160_/CLK                                Arrival: 249.826 ps
+[INFO GUI-0088] Register                                 _161_/CLK                                Arrival: 250.433 ps
+[INFO GUI-0088] Register                                 _162_/CLK                                Arrival: 249.956 ps
+[INFO GUI-0088] Register                                 ces_2_7/clock                            Arrival: 233.829 ps
+[INFO GUI-0088] Register                                 ces_3_6/clock                            Arrival: 243.645 ps
+[INFO GUI-0088] Register                                 ces_3_7/clock                            Arrival: 239.027 ps
+[INFO GUI-0088] Register                                 ces_0_0/clock                            Arrival: 290.815 ps
+[INFO GUI-0088] Register                                 ces_0_1/clock                            Arrival: 287.224 ps
+[INFO GUI-0088] Register                                 ces_0_2/clock                            Arrival: 276.359 ps
+[INFO GUI-0088] Register                                 ces_1_0/clock                            Arrival: 262.155 ps
+[INFO GUI-0088] Register                                 ces_1_1/clock                            Arrival: 258.349 ps
+[INFO GUI-0088] Register                                 ces_1_2/clock                            Arrival: 248.148 ps
+[INFO GUI-0088] Register                                 ces_0_3/clock                            Arrival: 226.049 ps
+[INFO GUI-0088] Register                                 ces_1_3/clock                            Arrival: 224.760 ps
+[INFO GUI-0088] Register                                 ces_0_4/clock                            Arrival: 242.883 ps
+[INFO GUI-0088] Register                                 ces_0_5/clock                            Arrival: 247.124 ps
+[INFO GUI-0088] Register                                 ces_1_4/clock                            Arrival: 237.497 ps
+[INFO GUI-0088] Register                                 ces_1_5/clock                            Arrival: 249.241 ps
+[INFO GUI-0088] Register                                 ces_1_6/clock                            Arrival: 253.384 ps
+[INFO GUI-0088] Register                                 ces_2_0/clock                            Arrival: 253.191 ps
+[INFO GUI-0088] Register                                 ces_2_1/clock                            Arrival: 248.850 ps
+[INFO GUI-0088] Register                                 ces_2_2/clock                            Arrival: 236.498 ps
+[INFO GUI-0088] Register                                 ces_3_0/clock                            Arrival: 261.042 ps
+[INFO GUI-0088] Register                                 ces_3_1/clock                            Arrival: 257.075 ps
+[INFO GUI-0088] Register                                 ces_3_2/clock                            Arrival: 244.640 ps
+[INFO GUI-0088] Register                                 ces_2_3/clock                            Arrival: 225.582 ps
+[INFO GUI-0088] Register                                 ces_2_4/clock                            Arrival: 239.450 ps
+[INFO GUI-0088] Register                                 ces_2_5/clock                            Arrival: 251.290 ps
+[INFO GUI-0088] Register                                 ces_2_6/clock                            Arrival: 255.456 ps
+[INFO GUI-0088] Register                                 ces_3_3/clock                            Arrival: 227.135 ps
+[INFO GUI-0088] Register                                 ces_3_4/clock                            Arrival: 243.496 ps
+[INFO GUI-0088] Register                                 ces_3_5/clock                            Arrival: 248.000 ps
+[INFO GUI-0088] Register                                 _163_/CLK                                Arrival: 253.020 ps
+[INFO GUI-0088] Register                                 _164_/CLK                                Arrival: 253.796 ps
+[INFO GUI-0088] Register                                 _165_/CLK                                Arrival: 254.691 ps
+[INFO GUI-0088] Register                                 _166_/CLK                                Arrival: 254.356 ps
+[INFO GUI-0088] Register                                 _167_/CLK                                Arrival: 254.200 ps
+[INFO GUI-0088] Register                                 _168_/CLK                                Arrival: 253.308 ps
+[INFO GUI-0088] Register                                 _169_/CLK                                Arrival: 252.967 ps
+[INFO GUI-0088] Register                                 _170_/CLK                                Arrival: 253.566 ps
+[INFO GUI-0088] Register                                 ces_4_6/clock                            Arrival: 236.291 ps
+[INFO GUI-0088] Register                                 ces_4_7/clock                            Arrival: 232.063 ps
+[INFO GUI-0088] Register                                 _171_/CLK                                Arrival: 231.291 ps
+[INFO GUI-0088] Register                                 _172_/CLK                                Arrival: 231.543 ps
+[INFO GUI-0088] Register                                 _173_/CLK                                Arrival: 231.174 ps
+[INFO GUI-0088] Register                                 _174_/CLK                                Arrival: 230.426 ps
+[INFO GUI-0088] Register                                 _175_/CLK                                Arrival: 231.306 ps
+[INFO GUI-0088] Register                                 _176_/CLK                                Arrival: 231.412 ps
+[INFO GUI-0088] Register                                 _177_/CLK                                Arrival: 231.484 ps
+[INFO GUI-0088] Register                                 _178_/CLK                                Arrival: 231.182 ps
+[INFO GUI-0088] Register                                 _179_/CLK                                Arrival: 244.957 ps
+[INFO GUI-0088] Register                                 _180_/CLK                                Arrival: 242.174 ps
+[INFO GUI-0088] Register                                 _181_/CLK                                Arrival: 244.902 ps
+[INFO GUI-0088] Register                                 _182_/CLK                                Arrival: 242.804 ps
+[INFO GUI-0088] Register                                 _183_/CLK                                Arrival: 244.575 ps
+[INFO GUI-0088] Register                                 _184_/CLK                                Arrival: 243.857 ps
+[INFO GUI-0088] Register                                 _185_/CLK                                Arrival: 242.949 ps
+[INFO GUI-0088] Register                                 _186_/CLK                                Arrival: 244.352 ps
+[INFO GUI-0088] Register                                 _187_/CLK                                Arrival: 253.289 ps
+[INFO GUI-0088] Register                                 _189_/CLK                                Arrival: 253.454 ps
+[INFO GUI-0088] Register                                 _193_/CLK                                Arrival: 253.757 ps
+[INFO GUI-0088] Register                                 _194_/CLK                                Arrival: 253.377 ps
+[INFO GUI-0088] Register                                 _188_/CLK                                Arrival: 249.940 ps
+[INFO GUI-0088] Register                                 _190_/CLK                                Arrival: 250.214 ps
+[INFO GUI-0088] Register                                 _191_/CLK                                Arrival: 250.193 ps
+[INFO GUI-0088] Register                                 _192_/CLK                                Arrival: 250.440 ps
+[INFO GUI-0088] Register                                 ces_6_6/clock                            Arrival: 237.794 ps
+[INFO GUI-0088] Register                                 ces_6_7/clock                            Arrival: 237.428 ps
+[INFO GUI-0088] Register                                 ces_7_6/clock                            Arrival: 248.387 ps
+[INFO GUI-0088] Register                                 ces_7_7/clock                            Arrival: 243.904 ps
+[INFO GUI-0088] Register                                 ces_4_0/clock                            Arrival: 269.870 ps
+[INFO GUI-0088] Register                                 ces_4_1/clock                            Arrival: 265.959 ps
+[INFO GUI-0088] Register                                 ces_4_2/clock                            Arrival: 254.121 ps
+[INFO GUI-0088] Register                                 ces_4_3/clock                            Arrival: 227.621 ps
+[INFO GUI-0088] Register                                 ces_5_0/clock                            Arrival: 260.539 ps
+[INFO GUI-0088] Register                                 ces_5_1/clock                            Arrival: 256.515 ps
+[INFO GUI-0088] Register                                 ces_5_2/clock                            Arrival: 245.174 ps
+[INFO GUI-0088] Register                                 ces_5_3/clock                            Arrival: 225.957 ps
+[INFO GUI-0088] Register                                 ces_5_4/clock                            Arrival: 233.418 ps
+[INFO GUI-0088] Register                                 ces_5_5/clock                            Arrival: 250.130 ps
+[INFO GUI-0088] Register                                 ces_5_6/clock                            Arrival: 260.323 ps
+[INFO GUI-0088] Register                                 ces_5_7/clock                            Arrival: 263.816 ps
+[INFO GUI-0088] Register                                 ces_4_4/clock                            Arrival: 219.267 ps
+[INFO GUI-0088] Register                                 ces_4_5/clock                            Arrival: 223.542 ps
+[INFO GUI-0088] Register                                 ces_7_0/clock                            Arrival: 287.112 ps
+[INFO GUI-0088] Register                                 ces_7_1/clock                            Arrival: 283.560 ps
+[INFO GUI-0088] Register                                 ces_7_2/clock                            Arrival: 273.081 ps
+[INFO GUI-0088] Register                                 ces_7_3/clock                            Arrival: 272.904 ps
+[INFO GUI-0088] Register                                 ces_6_0/clock                            Arrival: 250.403 ps
+[INFO GUI-0088] Register                                 ces_6_1/clock                            Arrival: 246.424 ps
+[INFO GUI-0088] Register                                 ces_6_2/clock                            Arrival: 235.488 ps
+[INFO GUI-0088] Register                                 ces_6_3/clock                            Arrival: 230.871 ps
+[INFO GUI-0088] Register                                 ces_6_4/clock                            Arrival: 234.553 ps
+[INFO GUI-0088] Register                                 ces_6_5/clock                            Arrival: 238.808 ps
+[INFO GUI-0088] Register                                 ces_7_4/clock                            Arrival: 240.051 ps
+[INFO GUI-0088] Register                                 ces_7_5/clock                            Arrival: 244.454 ps
+"""
+
+import re
+import matplotlib.pyplot as plt
+import numpy as np
+
+lines = text.strip().split('\n')
+filtered_lines = [line for line in lines if "ces" in line]
+
+# Finding the maximum indices for rows and columns
+max_row = max_col = 0
+data_dict = {}
+for line in filtered_lines:
+    match = re.search(r"ces_(\d+)_(\d+)/clock\s*Arrival:\s*(\d+\.\d+)", line)
+    if match:
+        row, col, value = map(int, map(float, match.groups()))
+        max_row = max(max_row, row)
+        max_col = max(max_col, col)
+        data_dict[(row, col)] = value
+
+# Constructing the data matrix
+data_matrix = np.zeros((max_row + 1, max_col + 1))
+for (row, col), value in data_dict.items():
+    data_matrix[row, col] = value
+
+# Plotting the heatmap
+plt.imshow(data_matrix, origin='upper', cmap='viridis', aspect='auto')
+plt.colorbar(label='Arrival (ps)')
+plt.title('Heatmap of Arrival Times')
+plt.xlabel('Column')
+plt.ylabel('Row')
+plt.show()
+```
+
+
+
+### oharboe
+The reason I was interested in the skew heatmap as a function of location, is that for the mock-array, it is more important to have low skew at the edges, where the input/output pins are, than in the center... If I understand the presentation correctly...
+
+From the heatmap, I can see that I get the "inverse" of what I am looking for: I get high latency/skew at the edges and lowest clock network latency in the middle of the array.
+
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/2a02ed4e-16d1-40cf-87cb-b356f6942acb)
+
+
+### oharboe
+Export to yaml everywhere? Then ask ChatGPT to write a program to graph whatever you want :-)
+
+### oharboe
+One more round of tinkering, extracting leaf latency (macros & flip flops) for mock-array:
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/f9324f3c-9b7d-4186-b202-73ddd958e478)
+
+```
+import numpy as np
+import matplotlib.pyplot as plt
+from scipy.interpolate import griddata
+from mpl_toolkits.mplot3d import Axes3D
+
+# Extract data from the table
+data = """
+[INFO GUI-0090] 353016 31894 _131_/CLK 2.5811525e-10
+[INFO GUI-0090] 353610 32704 _132_/CLK 2.578819e-10
+[INFO GUI-0090] 353448 29734 _133_/CLK 2.589441e-10
+[INFO GUI-0090] 353232 30004 _134_/CLK 2.5863567e-10
+[INFO GUI-0090] 353232 32164 _135_/CLK 2.5806945e-10
+[INFO GUI-0090] 353232 33514 _137_/CLK 2.5752672e-10
+[INFO GUI-0090] 352962 73474 _139_/CLK 2.4607233e-10
+[INFO GUI-0090] 353070 75094 _143_/CLK 2.455407e-10
+[INFO GUI-0090] 353232 74554 _145_/CLK 2.4536023e-10
+[INFO GUI-0090] 325488 49596 ces_0_7/clock 2.3215012e-10
+[INFO GUI-0090] 325488 97116 ces_1_7/clock 2.2571323e-10
+[INFO GUI-0090] 353070 30274 _136_/CLK 2.504758e-10
+[INFO GUI-0090] 353232 32974 _138_/CLK 2.5033728e-10
+[INFO GUI-0090] 353988 74824 _140_/CLK 2.468455e-10
+[INFO GUI-0090] 353070 74284 _141_/CLK 2.4607524e-10
+[INFO GUI-0090] 353124 73744 _142_/CLK 2.4646146e-10
+[INFO GUI-0090] 353718 74014 _144_/CLK 2.4688515e-10
+[INFO GUI-0090] 353070 75364 _146_/CLK 2.455602e-10
+[INFO GUI-0090] 282288 49596 ces_0_6/clock 2.3558674e-10
+[INFO GUI-0090] 354312 120724 _147_/CLK 2.396328e-10
+[INFO GUI-0090] 353070 120184 _148_/CLK 2.389033e-10
+[INFO GUI-0090] 353070 120724 _149_/CLK 2.3958044e-10
+[INFO GUI-0090] 353070 120454 _150_/CLK 2.3879088e-10
+[INFO GUI-0090] 352908 120994 _151_/CLK 2.3941804e-10
+[INFO GUI-0090] 354150 120994 _152_/CLK 2.3930402e-10
+[INFO GUI-0090] 353070 121264 _153_/CLK 2.387552e-10
+[INFO GUI-0090] 353070 121534 _154_/CLK 2.3849495e-10
+[INFO GUI-0090] 354312 167704 _155_/CLK 2.5028343e-10
+[INFO GUI-0090] 353070 167434 _156_/CLK 2.5006122e-10
+[INFO GUI-0090] 354312 167974 _157_/CLK 2.5054644e-10
+[INFO GUI-0090] 353070 167704 _158_/CLK 2.5003247e-10
+[INFO GUI-0090] 353502 168244 _159_/CLK 2.5076013e-10
+[INFO GUI-0090] 353070 167974 _160_/CLK 2.4982605e-10
+[INFO GUI-0090] 353070 168514 _161_/CLK 2.504333e-10
+[INFO GUI-0090] 353070 168784 _162_/CLK 2.4995647e-10
+[INFO GUI-0090] 325488 144636 ces_2_7/clock 2.3382915e-10
+[INFO GUI-0090] 282288 192156 ces_3_6/clock 2.4364535e-10
+[INFO GUI-0090] 325488 192156 ces_3_7/clock 2.3902733e-10
+[INFO GUI-0090] 23088 49596 ces_0_0/clock 2.908152e-10
+[INFO GUI-0090] 66288 49596 ces_0_1/clock 2.8722372e-10
+[INFO GUI-0090] 109488 49596 ces_0_2/clock 2.7635877e-10
+[INFO GUI-0090] 23088 97116 ces_1_0/clock 2.6215496e-10
+[INFO GUI-0090] 66288 97116 ces_1_1/clock 2.5834934e-10
+[INFO GUI-0090] 109488 97116 ces_1_2/clock 2.481484e-10
+[INFO GUI-0090] 152688 49596 ces_0_3/clock 2.2604922e-10
+[INFO GUI-0090] 152688 97116 ces_1_3/clock 2.2475981e-10
+[INFO GUI-0090] 195888 49596 ces_0_4/clock 2.4288263e-10
+[INFO GUI-0090] 239088 49596 ces_0_5/clock 2.4712393e-10
+[INFO GUI-0090] 195888 97116 ces_1_4/clock 2.3749708e-10
+[INFO GUI-0090] 239088 97116 ces_1_5/clock 2.492415e-10
+[INFO GUI-0090] 282288 97116 ces_1_6/clock 2.5338398e-10
+[INFO GUI-0090] 23088 144636 ces_2_0/clock 2.5319144e-10
+[INFO GUI-0090] 66288 144636 ces_2_1/clock 2.488505e-10
+[INFO GUI-0090] 109488 144636 ces_2_2/clock 2.3649802e-10
+[INFO GUI-0090] 23088 192156 ces_3_0/clock 2.6104152e-10
+[INFO GUI-0090] 66288 192156 ces_3_1/clock 2.5707544e-10
+[INFO GUI-0090] 109488 192156 ces_3_2/clock 2.4463978e-10
+[INFO GUI-0090] 152688 144636 ces_2_3/clock 2.2558208e-10
+[INFO GUI-0090] 195888 144636 ces_2_4/clock 2.394501e-10
+[INFO GUI-0090] 239088 144636 ces_2_5/clock 2.5129004e-10
+[INFO GUI-0090] 282288 144636 ces_2_6/clock 2.5545635e-10
+[INFO GUI-0090] 152688 192156 ces_3_3/clock 2.271353e-10
+[INFO GUI-0090] 195888 192156 ces_3_4/clock 2.4349614e-10
+[INFO GUI-0090] 239088 192156 ces_3_5/clock 2.4800043e-10
+[INFO GUI-0090] 353070 215224 _163_/CLK 2.5301994e-10
+[INFO GUI-0090] 354150 215764 _164_/CLK 2.5379573e-10
+[INFO GUI-0090] 352908 215764 _165_/CLK 2.546915e-10
+[INFO GUI-0090] 353016 215494 _166_/CLK 2.543563e-10
+[INFO GUI-0090] 352908 216034 _167_/CLK 2.5420016e-10
+[INFO GUI-0090] 353016 216304 _168_/CLK 2.53308e-10
+[INFO GUI-0090] 353070 216844 _169_/CLK 2.529667e-10
+[INFO GUI-0090] 353070 216574 _170_/CLK 2.5356642e-10
+[INFO GUI-0090] 282288 239676 ces_4_6/clock 2.362913e-10
+[INFO GUI-0090] 325488 239676 ces_4_7/clock 2.3206259e-10
+[INFO GUI-0090] 353556 262474 _171_/CLK 2.312914e-10
+[INFO GUI-0090] 353070 263014 _172_/CLK 2.3154262e-10
+[INFO GUI-0090] 353070 263284 _173_/CLK 2.3117369e-10
+[INFO GUI-0090] 353070 262744 _174_/CLK 2.3042566e-10
+[INFO GUI-0090] 353070 263824 _175_/CLK 2.3130639e-10
+[INFO GUI-0090] 353070 263554 _176_/CLK 2.3141243e-10
+[INFO GUI-0090] 353124 264094 _177_/CLK 2.3148382e-10
+[INFO GUI-0090] 354312 263554 _178_/CLK 2.3118188e-10
+[INFO GUI-0090] 353502 308644 _179_/CLK 2.4495708e-10
+[INFO GUI-0090] 353232 308914 _180_/CLK 2.421735e-10
+[INFO GUI-0090] 353394 309184 _181_/CLK 2.449023e-10
+[INFO GUI-0090] 352962 309454 _182_/CLK 2.428038e-10
+[INFO GUI-0090] 354204 309454 _183_/CLK 2.4457464e-10
+[INFO GUI-0090] 353664 309994 _184_/CLK 2.4385688e-10
+[INFO GUI-0090] 353070 309724 _185_/CLK 2.4294902e-10
+[INFO GUI-0090] 353664 310264 _186_/CLK 2.443524e-10
+[INFO GUI-0090] 353934 351844 _187_/CLK 2.53289e-10
+[INFO GUI-0090] 353016 353734 _189_/CLK 2.5345356e-10
+[INFO GUI-0090] 353016 354274 _193_/CLK 2.5375743e-10
+[INFO GUI-0090] 353556 352114 _194_/CLK 2.533773e-10
+[INFO GUI-0090] 353880 349684 _188_/CLK 2.4994018e-10
+[INFO GUI-0090] 353286 351574 _190_/CLK 2.502142e-10
+[INFO GUI-0090] 354042 349414 _191_/CLK 2.501929e-10
+[INFO GUI-0090] 353016 354004 _192_/CLK 2.5043992e-10
+[INFO GUI-0090] 282288 334716 ces_6_6/clock 2.3779426e-10
+[INFO GUI-0090] 325488 334716 ces_6_7/clock 2.374277e-10
+[INFO GUI-0090] 282288 382236 ces_7_6/clock 2.4838717e-10
+[INFO GUI-0090] 325488 382236 ces_7_7/clock 2.4390354e-10
+[INFO GUI-0090] 23088 239676 ces_4_0/clock 2.6987032e-10
+[INFO GUI-0090] 66288 239676 ces_4_1/clock 2.6595942e-10
+[INFO GUI-0090] 109488 239676 ces_4_2/clock 2.5412097e-10
+[INFO GUI-0090] 152688 239676 ces_4_3/clock 2.2762146e-10
+[INFO GUI-0090] 23088 287196 ces_5_0/clock 2.6053942e-10
+[INFO GUI-0090] 66288 287196 ces_5_1/clock 2.5651453e-10
+[INFO GUI-0090] 109488 287196 ces_5_2/clock 2.451736e-10
+[INFO GUI-0090] 152688 287196 ces_5_3/clock 2.2595725e-10
+[INFO GUI-0090] 195888 287196 ces_5_4/clock 2.334176e-10
+[INFO GUI-0090] 239088 287196 ces_5_5/clock 2.501299e-10
+[INFO GUI-0090] 282288 287196 ces_5_6/clock 2.6032337e-10
+[INFO GUI-0090] 325488 287196 ces_5_7/clock 2.6381633e-10
+[INFO GUI-0090] 195888 239676 ces_4_4/clock 2.1926745e-10
+[INFO GUI-0090] 239088 239676 ces_4_5/clock 2.2354223e-10
+[INFO GUI-0090] 23088 382236 ces_7_0/clock 2.871124e-10
+[INFO GUI-0090] 66288 382236 ces_7_1/clock 2.8355954e-10
+[INFO GUI-0090] 109488 382236 ces_7_2/clock 2.7308103e-10
+[INFO GUI-0090] 152688 382236 ces_7_3/clock 2.729042e-10
+[INFO GUI-0090] 23088 334716 ces_6_0/clock 2.504028e-10
+[INFO GUI-0090] 66288 334716 ces_6_1/clock 2.464243e-10
+[INFO GUI-0090] 109488 334716 ces_6_2/clock 2.3548827e-10
+[INFO GUI-0090] 152688 334716 ces_6_3/clock 2.3087125e-10
+[INFO GUI-0090] 195888 334716 ces_6_4/clock 2.3455274e-10
+[INFO GUI-0090] 239088 334716 ces_6_5/clock 2.388076e-10
+[INFO GUI-0090] 195888 382236 ces_7_4/clock 2.4005137e-10
+[INFO GUI-0090] 239088 382236 ces_7_5/clock 2.4445432e-10
+"""
+rows = data.strip().split("\n")
+x = []
+y = []
+z = []
+for row in rows:
+    _, _, x_val, y_val, _, z_val = row.split()
+    x.append(float(x_val))
+    y.append(float(y_val))
+    z.append(float(z_val)/1E-12)
+
+# Prepare grid for interpolation
+xi = np.linspace(min(x), max(x), 100)
+yi = np.linspace(min(y), max(y), 100)
+xi, yi = np.meshgrid(xi, yi)
+
+# Interpolate the z values
+zi = griddata((x, y), z, (xi, yi), method='linear')
+
+# Plot the 3D heatmap
+fig = plt.figure()
+ax = fig.add_subplot(111, projection='3d')
+surf = ax.plot_surface(xi, yi, zi, rstride=1, cstride=1, cmap=plt.cm.jet,
+                       linewidth=0, antialiased=False)
+
+fig.colorbar(surf)
+
+plt.show()
+```
+
+
+### oharboe
+asap7/sha3 using python snippet above...
+
+Animation: https://drive.google.com/file/d/1k64ew7QkB9AeRaFs9ZOX09EqzeMZupMG/view
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/01ef0594-b8dd-4188-b35d-1978d9ec762e)
+
+
+### maliberty
+@precisionmoon any thoughts here as I know you want more visualization as well.
+

FeatureRequest/3812.md

@@ -0,0 +1,34 @@
+# Feature to OpenROAD that lets us drag views with the mouse?
+
+Tool: Graphical User Interface
+
+Subcategory: User interface enhancement
+
+## Conversation
+
+### oharboe
+It would make moving around the design a lot easier.
+
+Is there a way to do this already?
+
+The arrow keys is a bit clunky compared to dragging the view with the mouse.
+
+### stefanottili
+OpenRoad will hopefully take hint's from KLayout's layout view controls instead of inventing yet another scheme.
+
+zoom in/out at the cursor position (mouse wheel zoom in/out)
+make the cursor key "shift width" adjustable (40% seem like a better value then the defaults)
+have "gestures" for fit, zoom in, zoom out (move mouse right-up, down, left-up), so no "mouse drag viewpoint".
+
+There doesn't seem to be a consensus for zoom in/out, fit, level down/up keys.
+I override the klayout defaults and use z/Z, f, l/L, curious what other people use.
+
+### stefanottili
+I stand corrected, there is dragging the view in Klayout, on a Mac is "right mouse + shift"
+
+### maliberty
+There is no method currently.  It could be an enhancement request as could gestures.
+
+### oharboe
+Added feature request https://github.com/The-OpenROAD-Project/OpenROAD/issues/3840
+

FeatureRequest/3856.md

@@ -0,0 +1,32 @@
+# Release scheme
+
+Subcategory: Release management
+
+## Conversation
+
+### Blebowski
+Hello,
+
+I see there is a lot of development going on. I am wondering whether there are any opinions/plans about introducing a release scheme (e.g. once a month or quarterly, or after major feature changes / enhancements) ? Maintaining something like `CHANGES.md` or `NEWS.md` would be also very handy. Once user does not follow the development almost day-to-day, it is easy to get lost.
+
+
+
+### QuantamHD
+I would be in favor of a news/changes file, but I'm a little bit more hesitant on slow releases. 
+
+Precision Innovations provides a daily release https://github.com/Precision-Innovations/OpenROAD/releases which I feel like is a good cadence given the fast pace of developement.
+
+I think slower stable releases make sense when you have an entity that's willing to cherry pick bug fixes into older releases, which we don't have yet. I feel like if we embraced a slower release process at this point in time the net result would be people stuck with bugs for longer.
+
+
+
+### mithro
+A monthly newsletter might be a good way to let people see the improvements.
+
+### dralabeing
+Daily releases are good to get the best , updated and stable versions especially with prebuilt binaries from the Precision releases.  I do think it would be good to add some sort of updates that are not yet in the docs or clear in the commit histories. For e.g mpl2 works well but this is not yet reflected in the default flow or docs but can be flagged in an Updates.md for users to try out --somewhat like a beta version. Similar any new features that are ready for use (partitioning, pin swapping,  gate cloning etc.) can be mentioned along with a special release tag .
+Monthly update frequency should be good as in special cases when an update is done sooner on a major feature.
+
+### rovinski
+I really like the [KLayout release notes](https://www.klayout.de/development.html) which have a list of PRs in that release (with hyperlinks) and a one-line description, as well as classifying as a bugfix or enhancement. It doesn't sound like we're moving from daily releases, but it could form a semi-automatically generated monthly newsletter or similar.
+

FeatureRequest/3939.md

@@ -0,0 +1,33 @@
+# Possible summary of changes format
+
+Subcategory: Release process enhancement
+
+## Conversation
+
+### vvbandeira
+While discussion #3856 has leaned to whether there should be a release and how frequent it should be, this discussion thread is to help guide the format and the process we would use to do such releases. We are considering using an automated way to generate "release notes" or at least a summary of recent changes. One proposed way to achieve this is to use PR titles and "Merge commit" messages. We would define and enforce a style of PR title, e.g., `[<TYPE>] <TOOL>: <SUMMARY>` where `[FEAT] drt: added shiny router cmd`. While `<TOOL>` is well defined (i.e., any module under `src/third-party` and `<SUMMARY>` will depend on the PR, what would be the most relevant values `<TYPE>` to include and their definition? As a starter point:
+
+- `[FEAT]` or `[NEW]`: for when we add new features, either in the form of Tcl/Python API changes -- e.g., new commands or flags.
+- `[DOCS]` or `[DOC]`: for documentation only changes.
+- `[BUGF]` or `[FIX]`: when fixing bugs or issues.
+- `[UPGR]` or `[ENH]`: upgrade/enhance -- not very sure about this, but it was what I thought with 4/3 letters to keep similar to above, mostly a self-imposed restriction, open to feedback.
+
+
+cc/ @maliberty @dralabeing @luarss @rovinski @QuantamHD 
+
+### maliberty
+I don't think of it as "summary of recent changes" as we still don't plan to do releases.  <TOOL> is also optional as some changes may span multiple tools though that should be less common.
+
+### rovinski
+I like the spirit, but I can foresee a few issues:
+
+1. A PR might span multiple tools, in which case it's hard to accommodate the format
+2. A PR might implement a feature only partially, in which case it's not ready for full use yet
+3. A PR might span multiple types (e.g. both feature and enhancement).
+4. If we want this scheme to stick, we will likely need a bot to enforce it or at least remind PR authors
+
+As such,
+
+* I think that enhancement and feature should probably just be one tag. I think PRs end up being both too often to distinguish
+* We need some sort of mechanism or identifying a feature as not ready for general use yet.
+

FeatureRequest/4420.md

@@ -0,0 +1,65 @@
+# Report total number of paths vs. number of failing path
+
+Tool: OpenSTA
+
+Subcategory: Reporting enhancement
+
+## Conversation
+
+### lustefan97
+I was wondering if there was a way to quickly summarize the ratio between the number of paths and number of failing paths (with regard to timing) using OpenSTA. I know it can report the slack in each path in a detailled manner, but I would like to have a report in the vein of : "Here is the number of paths that the design has that needs to be tested for timing vs. the number of path that failed the test"
+
+### maliberty
+I don't see an easy way as the number of paths is exponential.  How would you use the result?
+
+@tspyrou any thoughts?
+
+### oharboe
+@lustefan97 Could this be a use-case for timing histogram(supported in OpenROAD under Charts).
+
+### maliberty
+Note that to get the histograms you have to have qt charts installed.   During cmake you should get a message like "Charts widget is enabled" and not "Charts widget is not enabled"
+
+### maliberty
+> It is just a shame that it is so out if the way, I forget that we do... Can it be moved to the tabs where clocktree, hierarchy, etc. is?
+
+It is a docking window the same as all the others and can be position wherever you like.
+
+### maliberty
+> Anyway: I think it would be great if this feature could be made more available out of the box and not hidden away behind "cmake magic" and curious defaults.
+
+It is on by default, but qtcharts is not available for centos7 and so can't be assumed.
+
+### oharboe
+A less anaemic slack histogram example:
+
+```
+make DESIGN_CONFIG=designs/asap7/aes/config.mk cts
+```
+
+```
+make DESIGN_CONFIG=designs/asap7/aes/config.mk gui_cts
+```
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/1caeb16b-836f-4ae5-b5a6-6b235791ab90)
+
+
+### lustefan97
+@maliberty @oharboe Ok so I updated my OpenROAD to the latest version while having QT chart installed and enabled. After loading a database in that I knew had reported a slack, I tried to make a timing chart but resulted in the GUI crashing. 
+
+I got a warning telling me that timing data was not stored  in the database and must be loaded separately if needed, are they not stored in the .odb ? Is the .odb file only "geometric" (would not be surprising since a .lef and .def files are needed), even if .lib files and RC rules have been used to produce the final result ?
+
+### maliberty
+@AcKoucher FYI
+
+### oharboe
+@AcKoucher Just one more example of where the horizontal labels are gone completely:
+
+![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/7fa91044-d0df-4ffe-84b2-b5a264d959db)
+
+
+### lustefan97
+@oharboe @maliberty I have a quick but important question, right now I run my TCL scripts on a device that has no GUI, how would I need to proceed if I wanted to design a chip on it using OpenROAD but then move the results and generate the histogram on another computer (capable of opening a GUI).
+
+I ran a test script in which I saved the design in a .odb file and the timing results from OpenSTA in a .sdf file, but when I loaded the .odb back in another GUI session (as well as the .sdf file using `read_sdf`), multiple warnings were raised during loading and no histogram was created...
+

FeatureRequest/4422.md

@@ -0,0 +1,22 @@
+# Creating an FEOL Class in OpenROAD
+
+Subcategory: FEOL integration
+
+## Conversation
+
+### chetanyagoyal
+This is in regard to [https://github.com/chipsalliance/ideas/blob/main/gsoc-2023-ideas.md#create-feol-classes-in-openroad-and-a-gds-writer](url), a GSoC project proposed in 2023. I would like to take this up for 2024's run of GSoC, and was **wondering what the project entails**. For reference, I have been contributing to OpenFASoC for a large part of the year and have good knowledge of their codebase, and some knowledge of OpenROAD-flow-scripts
+
+### maliberty
+@msaligane was the mentor in 2023 so it would be good to get his input.  I expect the hardest part would be dealing with hierarchy (aref/sref) as OR's odb is rather flat in its lef/def orientation.   New layers shouldn't be too hard.  The rest of the system will have to be more aware of them and the GUI will need some updating.
+
+I would be good to have a specific use case beyond just read/write gds.  There should be some value added by doing it in OR as opposed to klayout or gdsfactory.
+
+### stefanottili
+Having openroad write gds/oas would be useful, because it reduces the file size compared to odb.
+
+But I would recommend not to duplicate the ability to read and collect all the gds/oas pieces coming from various other sources. This functionality already exists in strm2oas.
+
+### msaligane
+We have been looking into this in the previous GSOC. Hopefully, this project gets approved for Chetanya to finish the project.
+

FeatureRequest/4819.md

@@ -0,0 +1,19 @@
+# gui highlight_inst
+
+Tool: Graphical User Interface
+
+Subcategory: Enhance GUI functionality
+
+## Conversation
+
+### gyu511
+hello.
+In the gui, highlight_inst only supports up to 8 groups, so I would like to expand it to support more groups.
+So I added to HighlightGroupDialog in OpenROAD/src/gui/src/highlightGroupDialog.cpp and added color in OpenROAD/src/gui/include/gui/gui.h and finally button in OpenROAD/src/gui/ui/highlightGroupDlg.ui I also added it, but it doesn't work. What should I do?
+
+### maliberty
+Can you send a pointer to your branch with the changes?  How does it not work?
+
+### maliberty
+Once this works I hope you would be willing to make a PR so we can incorporate it in OR.
+

FeatureRequest/5041.md

@@ -0,0 +1,23 @@
+# Write macro placement position to a tcl file
+
+Tool: Hierarchical Macro Placement
+
+Subcategory: Macro placement output
+
+## Conversation
+
+### vijayank88
+Similar to `write_pin_placement` option, is there a option to write macro placement position while using automatic macro placement.
+So that macro position will be re-used for some specific requirement with manual macro placement again.
+
+### maliberty
+This is more of an issue than a discussion
+
+### maliberty
+https://github.com/The-OpenROAD-Project/OpenROAD/issues/5043
+
+### AcKoucher
+@vijayank88 FYI, there's the `write_macro_placement` flag in mpl2. However it's currently deprecated due to a new OR command for general macro placement writing that was implemented in #4557.
+
+I've opened #5046 to update the flag so that mpl2 will write the entire macro placement instead of only those macros that it placed.
+

FeatureRequest/5420.md

@@ -0,0 +1,24 @@
+# dft command names
+
+Tool: Design for Test
+
+Subcategory: Command naming
+
+## Conversation
+
+### ThomasGeroudet
+Hello @maliberty, @fgaray, I've just seen dft commands, but not tried it yet.
+The name of the commands seemed familiar, and I was wondering if it could be better to rename them to avoid potential legal issues such as this one:
+https://news.synopsys.com/2016-12-21-Synopsys-Obtains-Injunction-in-Copyright-Suit-Against-ATopTech
+In case of renaming, maybe all dft commands could start with dft_* so that it's easy to find them ?
+
+### fgaray
+Yeah, changing the names SGTM to avoid this issue.
+
+Do we know what other tools use to name this commands? (Cadence for example). I tried looking online but could not find Cadence's related docs.
+
+dft_insert, dft_scan_replace, dft_preview SGTM
+
+### maliberty
+Thanks, we want to avoid any such conflicts.  I am not aware of the proprietary tool names but am fine with a rename to avoid such.
+

Installation/2679.md

@@ -0,0 +1,37 @@
+# How can I run the OpenROAD GUI on Ubuntu locally and not in Docker?
+
+Tool: Graphical User Interface
+
+Subcategory: Local installation
+
+## Conversation
+
+### oharboe
+How can I install and run the OpenROAD GUI locally?
+
+I want the advantages of Docker, not having to install everything, easy to deploy upgrades, but when I run the OpenROAD GUI from docker, the experience is pretty good, but not quite as good as running locally on Ubuntu.
+
+Another problem is that the OpenROAD-flow-scripts sets up a TON of environment variables, even if I had OpenROAD GUI installed locally, how could I get the envioronment set up correctly as I build various designs?
+
+Example of how I run the OpenROAD GUI in Docker. To run my own designs, I map results, log, objects, designs to my local drive by modifying the script in the github issue below.
+
+https://github.com/The-OpenROAD-Project/OpenROAD/issues/2675#issue-1513733033
+
+
+Ideally I'd like a debian package for the OpenROAD GUI. It seems like it should be possible to host a debian package on github, but it is a bit of work, especially considering that it probably needs to be built nightly to be truely useful in the open soruce development process: https://assafmo.github.io/2019/05/02/ppa-repo-hosted-on-github.html
+
+
+
+### QuantamHD
+Creating a snap package in the CI might be a good option https://ubuntu.com/tutorials/create-your-first-snap#1-overview
+
+### maliberty
+You would run the [dependency installer](https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/etc/DependencyInstaller.sh) and then compiler OR locally  (build_openroad.sh --local).
+
+I'm surprised using docker makes much of a difference for the GUI.  What do you see?
+
+You can always mount your directory in docker so envars shouldn't be a big issue.
+
+### mithro
+Have you tried the conda packages?
+

Installation/2971.md

@@ -0,0 +1,43 @@
+# Arm64 Support
+
+Subcategory: Architecture compatibility
+
+## Conversation
+
+### DylanTom
+Hi, I am looking to use OpenROAD and have tried to install it on my computer.
+
+It is an M2 Pro Macbook Pro, 32 GB RAM, 1TB SSD. I am running an Ubuntu VM through UTM which has 8GB RAM and 64 GB SSD. 
+
+I am having trouble with building OpenROAD because one of the dependencies is `or-tools`, which does not appear to have Ubuntu support for the ARM architecture. I was wondering if anyone had similar issues or would know how to resolve this.
+
+Specifically, does OpenROAD support the ARM architecture, and if not, is that a priority in the future? 
+
+Thanks!
+
+### vijayank88
+Can you try OpenROAD-flow-scripts with docker based: https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildWithDocker.html#clone-and-build
+
+### maliberty
+We do not officially support it as we don't have the hardware resources to test on that platform.  We do try to make sure we can compile on mac M1 based systems.  That said or-tools is available for arm64 as Vijayan pointed out.
+
+### vvbandeira
+> Note: OR-Tools only provides archives for the x86_64 (also known as amd64) architecture.
+Source: https://developers.google.com/optimization/install/cpp/binary_linux
+
+@DylanTom If you are already using a VM, you can create a x86_64 VM and avoid this issue.
+
+### stefanottili
+If you're on M2, why not give "native" OR a try ?
+
+I've been compiling it on and off using HomeBrew for dependencies (including or-tools) for a while now.
+or-tools and mpl2 keep on breaking the build and mpl2 is still be disabled.
+>> -- Removing MPL2 and PAR to avoid run time fatal error.
+
+So occasionally it doesn't work, but most of the times I got it to compile in < 15min on a M1.
+
+etc/DependencyInstaller.sh     (unforunately now installs x86 klayout, I prefer building it natively)
+./build_openroad.sh --local --latest --clean-force   (breaks today in a mpl2 test)
+./build_openroad.sh --local   (when run again it finishes, go figure)
+
+

Installation/2972.md

@@ -0,0 +1,102 @@
+# CMAKE errors while installing Openroad
+
+Subcategory: Build issues
+
+## Conversation
+
+### mdzaki-git
+HI All,
+
+After installing the dependencies we re stuck with cmake errors and would appreciate your help in fixing them. Attaching the error snippet for reference.
+<img width="1388" alt="Cmake Error" src="https://user-images.githubusercontent.com/68725332/223042193-39b47832-730e-4716-abce-421e7a44dfc8.png">
+
+
+### vijayank88
+attach log `build_openroad.log`
+
+### mdzaki-git
+[openroad_build.log](https://github.com/The-OpenROAD-Project/OpenROAD/files/10897535/openroad_build.log)
+
+
+### mdzaki-git
+Following the install instruction mentioned on git hub.
+https://github.com/The-OpenROAD-Project/OpenROAD
+
+### mdzaki-git
+Hi Vitor,
+
+Recloned the repository and tried again, getting below errors now.
+
+
+
+On Mon, Mar 6, 2023 at 7:32 PM Vitor Bandeira ***@***.***>
+wrote:
+
+> @vijayank88 <https://github.com/vijayank88>, this warning is not a
+> problem with CMake; this indicates that the folder is not a git repo.
+> @mdzaki-git <https://github.com/mdzaki-git>, can you make sure that the
+> clone ended fine? Maybe check the output of git status --long, the output
+> of this command should look something like this:
+>
+> > git status --long
+> On branch master
+> Your branch is up to date with 'origin/master'.
+> nothing to commit, working tree clean
+>
+> Also, try to do a clean build and in case of any errors upload the new log
+> file.
+>
+> ./etc/Build.sh -clean
+>
+> —
+> Reply to this email directly, view it on GitHub
+> <https://github.com/The-OpenROAD-Project/OpenROAD/discussions/2972#discussioncomment-5216244>,
+> or unsubscribe
+> <https://github.com/notifications/unsubscribe-auth/AQMKUVEUTV4F7PDCH6F4IQ3W2XU6HANCNFSM6AAAAAAVQXMFI4>
+> .
+> You are receiving this because you were mentioned.Message ID:
+> <The-OpenROAD-Project/OpenROAD/repo-discussions/2972/comments/5216244@
+> github.com>
+>
+
+
+### mdzaki-git
+[openroad_build.log](https://github.com/The-OpenROAD-Project/OpenROAD/files/10899446/openroad_build.log)
+
+
+### vvbandeira
+Looks like you missed the `--recursive` when cloning. Please run
+
+```
+git submodule update --init
+```
+
+In the future you should use `git clone --recursive` to also clone the submodules `abc` and `sta`. 
+
+### mdzaki-git
+Hi All,
+
+Thanks it works now.
+
+On Mon, Mar 6, 2023 at 9:37 PM Vitor Bandeira ***@***.***>
+wrote:
+
+> Looks like you missed the --recursive when cloning. Please run
+>
+> git submodule update --init
+>
+> In the future you should use git clone --recursive to also clone the
+> submodules abc and sta.
+>
+> —
+> Reply to this email directly, view it on GitHub
+> <https://github.com/The-OpenROAD-Project/OpenROAD/discussions/2972#discussioncomment-5217710>,
+> or unsubscribe
+> <https://github.com/notifications/unsubscribe-auth/AQMKUVH4OMC266IZBNAHYATW2YDTFANCNFSM6AAAAAAVQXMFI4>
+> .
+> You are receiving this because you were mentioned.Message ID:
+> <The-OpenROAD-Project/OpenROAD/repo-discussions/2972/comments/5217710@
+> github.com>
+>
+
+