espsluar commited on
Commit
aad6d66
·
verified ·
1 Parent(s): fd15ddd

Delete gh_discussions

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. gh_discussions/Bug/3217.md +0 -25
  2. gh_discussions/Bug/3314.md +0 -138
  3. gh_discussions/Bug/3362.md +0 -60
  4. gh_discussions/Bug/3589.md +0 -26
  5. gh_discussions/Bug/3597.md +0 -53
  6. gh_discussions/Bug/4163.md +0 -29
  7. gh_discussions/Bug/4845.md +0 -34
  8. gh_discussions/Bug/5333.md +0 -48
  9. gh_discussions/Build/1951.md +0 -25
  10. gh_discussions/Build/2330.md +0 -50
  11. gh_discussions/Build/2342.md +0 -51
  12. gh_discussions/Build/2952.md +0 -104
  13. gh_discussions/Build/3094.md +0 -50
  14. gh_discussions/Build/3124.md +0 -43
  15. gh_discussions/Build/3148.md +0 -51
  16. gh_discussions/Build/3489.md +0 -26
  17. gh_discussions/Build/3513.md +0 -33
  18. gh_discussions/Build/3779.md +0 -19
  19. gh_discussions/Build/4137.md +0 -1565
  20. gh_discussions/Build/4269.md +0 -52
  21. gh_discussions/Build/4956.md +0 -67
  22. gh_discussions/Build/5101.md +0 -31
  23. gh_discussions/Configuration/2442.md +0 -20
  24. gh_discussions/Configuration/3350.md +0 -41
  25. gh_discussions/Configuration/3943.md +0 -35
  26. gh_discussions/Configuration/4289.md +0 -31
  27. gh_discussions/Configuration/4515.md +0 -23
  28. gh_discussions/Configuration/5065.md +0 -155
  29. gh_discussions/Configuration/5199.md +0 -24
  30. gh_discussions/Configuration/5213.md +0 -66
  31. gh_discussions/Documentation/4495.md +0 -27
  32. gh_discussions/Documentation/5312.md +0 -34
  33. gh_discussions/Installation/2679.md +0 -37
  34. gh_discussions/Installation/2971.md +0 -43
  35. gh_discussions/Installation/2972.md +0 -102
  36. gh_discussions/Installation/3004.md +0 -107
  37. gh_discussions/Installation/4162.md +0 -23
  38. gh_discussions/Installation/4653.md +0 -20
  39. gh_discussions/Query/1539.md +0 -21
  40. gh_discussions/Query/1610.md +0 -144
  41. gh_discussions/Query/1732.md +0 -52
  42. gh_discussions/Query/1870.md +0 -20
  43. gh_discussions/Query/2083.md +0 -93
  44. gh_discussions/Query/2745.md +0 -305
  45. gh_discussions/Query/2800.md +0 -24
  46. gh_discussions/Query/2868.md +0 -130
  47. gh_discussions/Query/2923.md +0 -55
  48. gh_discussions/Query/2927.md +0 -22
  49. gh_discussions/Query/2965.md +0 -33
  50. gh_discussions/Query/3023.md +0 -18
gh_discussions/Bug/3217.md DELETED
@@ -1,25 +0,0 @@
1
- # DRC error in detailed routing - Short
2
-
3
- Tool: Detailed Routing
4
-
5
- Subcategory: Routing violation
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- What is detailed routing trying to do here? The grey area is a macro.
11
-
12
- Is the detailed route simply spilling onto the macro because it can't find a valid place to put the wire?
13
-
14
- ![image](https://user-images.githubusercontent.com/2798822/233313803-be73a31c-255b-4857-acb3-d304cb37db11.png)
15
-
16
-
17
- ![image](https://user-images.githubusercontent.com/2798822/233314427-9f2f4378-db70-4f2f-bc54-c23118c5e2b9.png)
18
-
19
-
20
- ### oharboe
21
- Since no-one answers, I'm thinking I guessed right :-)
22
-
23
- ### maliberty
24
- Most likely (assuming the layers are blocked and this isn't just available resource).
25
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/3314.md DELETED
@@ -1,138 +0,0 @@
1
- # [WARNING STA-0139] ... 63.3687 is not a float.
2
-
3
- Tool: OpenSTA
4
-
5
- Subcategory: Locale issue
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- I get a lot of these warnings when I run `make gui_final`
11
-
12
- This is with the latest ORFS.
13
-
14
- What are they?
15
-
16
- ```
17
- $ make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk place
18
- ```
19
-
20
-
21
- ```
22
- [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.
23
- [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.
24
- [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.
25
- [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.
26
- [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.
27
- [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.
28
- [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.
29
- [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.
30
- [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.
31
- [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.
32
- [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.
33
- [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.
34
- [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.
35
- [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.
36
- [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.
37
- [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.
38
- [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.
39
- ```
40
-
41
- ### vijayank88
42
- @oharboe
43
- I ran with latest commit and not able to get similar logs.
44
-
45
- ### maliberty
46
- 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.
47
-
48
- ### oharboe
49
- ```
50
- rm -rf results/
51
- make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk place
52
- make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk gui_place
53
- ```
54
-
55
- ```
56
- $ make DESIGN_CONFIG=designs/asap7/mock-array-big/Element/config.mk gui_place
57
- [INFO][FLOW] Using platform directory ./platforms/asap7
58
- [INFO-FLOW] ASU ASAP7 - version 2
59
- Default PVT selection: BC
60
- 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
61
- Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
62
- This plugin does not support propagateSizeHints()
63
- OpenROAD v2.0-8114-gaa1f8060d
64
- This program is licensed under the BSD-3 license. See the LICENSE file for details.
65
- Components of this program may be licensed under more restrictive licenses which must be honored.
66
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 0.72 is not a float.
67
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 1.44 is not a float.
68
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 2.88 is not a float.
69
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 5.76 is not a float.
70
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 11.52 is not a float.
71
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 23.04 is not a float.
72
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 82, 46.08 is not a float.
73
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 0.72 is not a float.
74
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 1.44 is not a float.
75
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 2.88 is not a float.
76
- [WARNING STA-0139] ./platforms/asap7/lib/asap7sc7p5t_AO_RVT_FF_nldm_211120.lib.gz line 96, 5.76 is not a float.
77
- ```
78
-
79
-
80
- ### oharboe
81
- @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.
82
-
83
- The evidence that this is the problem is that setting `LC_NUMERIC="en_GB.UTF-8"` fixes the problem.
84
-
85
- In this case, the locale is decided by the format that is being parsed, it is not a human readable/writeable number.
86
-
87
- Let's see if this works: https://github.com/Pinata-Consulting/OpenSTA/tree/lock-down-strtof-locale
88
-
89
- Yep :-)
90
-
91
- This also explains why we don't see this when we run from docker, only local install.
92
-
93
- ### maliberty
94
- 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?
95
-
96
- ### maliberty
97
- 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?
98
-
99
-
100
- ### maliberty
101
- 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?
102
-
103
- ### oharboe
104
- @maliberty @luis201420 With this change, I no longer get the warnings.
105
-
106
- 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 :-)
107
-
108
- ```
109
- diff --git a/src/gui/src/gui.cpp b/src/gui/src/gui.cpp
110
- index 355aa6842..7d79d99a3 100644
111
- --- a/src/gui/src/gui.cpp
112
- +++ b/src/gui/src/gui.cpp
113
- @@ -1141,6 +1141,16 @@ int startGui(int& argc,
114
- }
115
- main_window->show();
116
-
117
- + // This avoids problems with locale setting dependent
118
- + // C functions like strtod (e.g. 0.5 vs 0,5).
119
- + std::array locales = {"en_US.UTF-8", "C.UTF-8", "C"};
120
- + for (auto locale : locales) {
121
- + if (std::setlocale(LC_ALL, locale) != nullptr) {
122
- + break;
123
- + }
124
- + }
125
- +
126
- +
127
- gui->setLogger(open_road->getLogger());
128
-
129
- main_window->setDatabase(open_road->getDb());
130
- ```
131
-
132
-
133
- ### maliberty
134
- @luis201420 will you look at this since you can reproduce it
135
-
136
- ### oharboe
137
- 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.
138
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/3362.md DELETED
@@ -1,60 +0,0 @@
1
- # Where does "Error: tdms_place.tcl, 35 cannot create std::vector larger than max_size()"
2
-
3
- Tool: Global Placement
4
-
5
- Subcategory: Memory allocation error
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- I want to debug it, but I searched the code and couldn't find this error message in the source.
11
-
12
- ```
13
- [INFO GPL-0003] SiteSize: 54 270
14
- [INFO GPL-0004] CoreAreaLxLy: 2160 2160
15
- [INFO GPL-0005] CoreAreaUxUy: 25922160 25922160
16
- Error: tdms_place.tcl, 35 cannot create std::vector larger than max_size()
17
- Command exited with non-zero status 1
18
- ```
19
-
20
-
21
- ### maliberty
22
- 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.
23
-
24
- ### oharboe
25
- This is odd... 48000*96000 = 4608000000. Ah. overflow.
26
-
27
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/ca384a53-04da-42fd-9039-014b3bdd89f9)
28
-
29
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/a0156546-48aa-4c6c-84a1-ee9b89647226)
30
-
31
-
32
- ```
33
- D$ git diff
34
- diff --git a/src/gpl/src/placerBase.cpp b/src/gpl/src/placerBase.cpp
35
- index 30ff82771..4f2c10b4e 100644
36
- --- a/src/gpl/src/placerBase.cpp
37
- +++ b/src/gpl/src/placerBase.cpp
38
- @@ -1002,8 +1002,8 @@ void PlacerBase::initInstsForUnusableSites()
39
- {
40
- dbSet<dbRow> rows = db_->getChip()->getBlock()->getRows();
41
-
42
- - int siteCountX = (die_.coreUx() - die_.coreLx()) / siteSizeX_;
43
- - int siteCountY = (die_.coreUy() - die_.coreLy()) / siteSizeY_;
44
- + long siteCountX = (die_.coreUx() - die_.coreLx()) / siteSizeX_;
45
- + long siteCountY = (die_.coreUy() - die_.coreLy()) / siteSizeY_;
46
-
47
- enum PlaceInfo
48
- {
49
- ```
50
-
51
- gives me:
52
-
53
- ```
54
- [INFO GPL-0002] DBU: 1000
55
- [INFO GPL-0003] SiteSize: 54 270
56
- [INFO GPL-0004] CoreAreaLxLy: 2160 2160
57
- [INFO GPL-0005] CoreAreaUxUy: 25922160 25922160
58
- Error: out of memory.
59
- ```
60
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/3589.md DELETED
@@ -1,26 +0,0 @@
1
- # how to fix metal spacing DRCs
2
-
3
- Tool: Detailed Routing
4
-
5
- Subcategory: DRC violation
6
-
7
- ## Conversation
8
-
9
- ### gkamendje
10
- 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?
11
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/56942214/af73acfe-92fb-4590-baaf-31be8548e95e)
12
-
13
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/56942214/4ed7f795-fef7-4d49-9f78-76b85c9cae37)
14
-
15
-
16
-
17
- ### maliberty
18
- Can you provide a test case?
19
-
20
- ### maliberty
21
- You have very wide METAL1 power stripes:
22
-
23
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/761514/ec146977-bcb3-4725-8140-4bef3c0137ef)
24
-
25
- 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.
26
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/3597.md DELETED
@@ -1,53 +0,0 @@
1
- # Detailed routing loops instead of straight wire...
2
-
3
- Tool: Detailed Routing
4
-
5
- Subcategory: Routing pattern anomaly
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- I've been fixing some problems in mock-array in positioning of macros and pins not being aligned and now things are working well.
11
-
12
- However, I found this curious thing when inspecting, a detailed routing loop :-)
13
-
14
- I don't see any reason why a horizontal wire wouldn't work here...
15
-
16
- Any ideas or insights?
17
-
18
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/381a3158-6635-452c-a270-247df28a6dae)
19
-
20
-
21
- The above can be found if creating a `flow/settings.mk` file:
22
-
23
- ```
24
- export DESIGN_CONFIG?=designs/asap7/mock-array/config.mk
25
- export MOCK_ARRAY_DATAWIDTH?=8
26
- export MOCK_ARRAY_TABLE?=8 8 4 4 5 5
27
- export MOCK_ARRAY_SCALE?=80
28
- ```
29
-
30
- and running `make verilog` and `make`
31
-
32
-
33
- Various interesting things can be seen in detailed routing:
34
-
35
- - almost all the wires are vertical/horizontal between "Element" macros. The loop above is untypical, usually it's just a slight horizontal/vertical deviation.
36
- - there are hold cells in the middle to the right
37
-
38
-
39
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/e9bca2da-5e41-4ee6-b279-e7ca375bb26a)
40
-
41
-
42
-
43
- Hold cells have to be placed *outside* to the right of the array, hence many non-vertical vertical wires between those two elements.
44
-
45
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/3a17be46-8604-498c-901f-ce375cbed5cc)
46
-
47
-
48
- ### maliberty
49
- @osamahammad21 any thoughts on the loop?
50
-
51
- ### oharboe
52
- A feature request filed: https://github.com/The-OpenROAD-Project/OpenROAD/issues/3634
53
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/4163.md DELETED
@@ -1,29 +0,0 @@
1
- # [WARNING GRT-0350] Missing route to pin iregister_read/io_bypass_1_bits_data[0].
2
-
3
- Tool: Global Routing
4
-
5
- Subcategory: Parasitics estimation issue
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- This is for the top level of MegaBoom that I'm playing around with.
11
-
12
- Is this warning telling me that it can't find a route for the buffer tree for the pin in the warning?
13
-
14
- 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...
15
-
16
-
17
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/e3c6b965-bf83-403c-9dd5-70413735a8ca)
18
-
19
-
20
-
21
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/2798822/c2a76f06-f286-4b5a-8bc7-2fc0219bc9f8)
22
-
23
-
24
- ### maliberty
25
- @eder-matheus please respond
26
-
27
- ### eder-matheus
28
- @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.
29
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/4845.md DELETED
@@ -1,34 +0,0 @@
1
- # Is [read_def -floorplan_initialize ] expected to unset [set_max_transition] and [set_max_capacitance] from sdc file?
2
-
3
- Tool: Initialize Floorplan
4
-
5
- Subcategory: Unexpected behavior
6
-
7
- ## Conversation
8
-
9
- ### b62833
10
- Before I file a bug, I want to make sure this is unexpected behavior.
11
-
12
- In my sdc file I do a
13
- ```
14
-
15
- set_max_transition [exp $clk_period * 0.20] [current_design]
16
- set_max_capacitance 30 [current_design]
17
- ```
18
-
19
- and then read a floorplan by setting FLOORPLAN_DEF.
20
-
21
- 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?
22
-
23
-
24
-
25
- ### maliberty
26
- I would consider it unexpected so go ahead and open an issue with a test case
27
-
28
- ### b62833
29
- Over the weekend I upgraded to OpenROAD version 2.0-13286-gebcc5196e and it works now.
30
-
31
- It was broken in the version v2.0-11493-gaddecc2bd that I'd been using before.
32
-
33
- We're good now.
34
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Bug/5333.md DELETED
@@ -1,48 +0,0 @@
1
- # pdgen remove stripes with [WARNING PDN-0200] Removing floating shape:
2
-
3
- Tool: Power Distribution Network Generator
4
-
5
- Subcategory: Power distribution network issue
6
-
7
- ## Conversation
8
-
9
- ### titan73
10
- Based on the example at the bottom of https://openroad.readthedocs.io/en/latest/main/src/pdn/README.html.
11
-
12
- I did the following floorplan with the .def containing the power pins:
13
-
14
- read_def -floorplan_initialize floor.def
15
- set fp_area [ord::get_die_area]
16
- initialize_floorplan -die_area $fp_area -core_area $fp_area -site CORECUBRICK
17
-
18
- add_global_connection -net VDDD -pin_pattern {^VDDD$} -power
19
- add_global_connection -net GNDD -pin_pattern {^GNDD$} -ground
20
-
21
- set_voltage_domain -power VDDD -ground GNDD
22
-
23
- define_pdn_grid -name "Core"
24
- add_pdn_ring -grid "Core" -layers {metal4B alucap} -widths 5.0 -spacings 2.0 -core_offsets 4.5 -connect_to_pads
25
-
26
- add_pdn_stripe -followpins -layer metal1 -extend_to_core_ring
27
-
28
- add_pdn_stripe -layer metal4B -width 0.48 -pitch 56.0 -offset 2.0 -extend_to_core_ring
29
- add_pdn_stripe -layer alucap -width 1.40 -pitch 40.0 -offset 2.0 -extend_to_core_ring
30
-
31
- add_pdn_connect -layers {metal4B alucap}
32
- add_pdn_connect -layers {alucap metal4B}
33
-
34
- pdngen
35
-
36
- The sroutes and the ring are created but not the stripes and I get the the warnings:
37
-
38
- [WARNING PDN-0200] Removing floating shape: GNDD (1.7600, -9.5000) - (2.2400, 821.3000) on metal4B
39
- [WARNING PDN-0200] Removing floating shape: VDDD (29.7600, -16.5000) - (30.2400, 828.3000) on metal4B
40
-
41
- Is there something more to do to connect these shapes?
42
-
43
- ### titan73
44
- Also note that the related power pins imported the from .def are removed.
45
-
46
- ### maliberty
47
- Can you provide a test case? Its hard to say much from just the output
48
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/1951.md DELETED
@@ -1,25 +0,0 @@
1
- # Is it possible to generate a static binary of OpenROAD?
2
-
3
- Subcategory: Static binary generation
4
-
5
- ## Conversation
6
-
7
- ### TiagoAFontana
8
- 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.
9
-
10
- 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.
11
-
12
- Does someone know how to do this?
13
-
14
- ### vijayank88
15
- @vvbandeira Any suggestion?
16
-
17
- ### QuantamHD
18
- Bazel rules hdl supports fully static builds of openroad.
19
-
20
- Just download bazel, git clone https://github.com/hdl/bazel_rules_hdl
21
-
22
- And run bazel build @org_theopenroadproject//:openroad in the git repo.
23
-
24
- It also statically builds the entire dependency chain of openroad from source.
25
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/2330.md DELETED
@@ -1,50 +0,0 @@
1
- # Compilation Error
2
-
3
- Subcategory: Compilation error
4
-
5
- ## Conversation
6
-
7
- ### gudeh
8
- Hey guys! I am getting the following compilation error:
9
-
10
- > [100%] Linking CXX executable openroad
11
- > 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
12
- > /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
13
- > /usr/bin/ld: drt/drt.a(TritonRoute.cpp.o): in function \`boost::archive::basic_binary_iarchive<fr::frIArchive>::init()':
14
- > 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)'
15
- > collect2: error: ld returned 1 exit status
16
- > make[2]: *** [src/CMakeFiles/openroad.dir/build.make:210: src/openroad] Error 1
17
- > make[2]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
18
- > make[1]: *** [CMakeFiles/Makefile2:449: src/CMakeFiles/openroad.dir/all] Error 2
19
- > make[1]: *** Waiting for unfinished jobs....
20
- > [100%] Linking CXX executable trTest
21
- > 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
22
- > /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
23
- > make[2]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
24
- > [100%] Built target trTest
25
- > make[1]: Leaving directory '/home/gudeh/Documents/OpenROAD-flow-scripts/tools/OpenROAD/build'
26
- > make: *** [Makefile:133: all] Error 2
27
-
28
- The error I pasted here is from a clean clone from the flow repository. I did the following commands to get to this error:
29
-
30
- > git clone --recursive https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts
31
- > cd OpenROAD-flow-scripts
32
- > sudo ./tools/OpenROAD/etc/DependencyInstaller.sh -dev
33
- > ./build_openroad.sh --local
34
-
35
- 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.
36
-
37
- ### maliberty
38
- What OS and what compiler?
39
-
40
- ### maliberty
41
- 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?
42
-
43
- ### gudeh
44
- 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.
45
-
46
- It seems that for some reason the DependencyInstaller didn't fetch the correct Boost version to upgrade to.
47
-
48
- ### maliberty
49
- @vvbandeira any idea about " for some reason the DependencyInstaller didn't fetch the correct Boost version to upgrade to."?
50
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/2342.md DELETED
@@ -1,51 +0,0 @@
1
- # Apple clang 14.0.0 (Xcode 14.0.1) M1 coredumps compiling abc .c files
2
-
3
- Tool: ABC
4
-
5
- Subcategory: Compiler crash
6
-
7
- ## Conversation
8
-
9
- ### stefanottili
10
- Hi Folks,
11
-
12
- just a heads up for anybody using an Apple M1 with the most recent Xcode 14.0.1
13
-
14
- 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.
15
-
16
- I was able to compile OpenROAD on this machine before, but not with the latest and greatest Xcode.
17
-
18
- I'm curious whether there are other M1/Xcode users out there with similar experience.
19
-
20
- Stefan
21
-
22
- gmake[2]: Entering directory '/Users/user/OpenROAD-flow-scripts/tools/OpenROAD/build'
23
- [ 0%] Building CXX object third-party/abc/CMakeFiles/libabc.dir/src/misc/extra/extraUtilMisc.c.o
24
- 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
25
- clang: error: unable to execute command: Segmentation fault: 11
26
- clang: error: clang frontend command failed due to signal (use -v to see invocation)
27
- Apple clang version 14.0.0 (clang-1400.0.29.102)
28
- Target: arm64-apple-darwin21.6.0
29
- Thread model: posix
30
- InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
31
-
32
-
33
- ### stefanottili
34
- downgrading the command line tools to 13.4 allows to build the project
35
-
36
- ### stefanottili
37
- Here's some feedback from https://developer.apple.com/forums/thread/717259
38
-
39
- > It only happens with optimized code. An alternative workaround for building openroad is to patch the abc cmake file to include -g
40
-
41
- third-party/CMakeLists.txt @@ -46,6 +46,10 @@ if (NOT USE_SYSTEM_ABC)
42
- readline is not needed since we call abc from c++
43
- set(READLINE_FOUND FALSE)
44
- +# apple clang 14.0.0 seg faults on abc without -g +add_compile_options(
45
- $<$<CXX_COMPILER_ID:AppleClang>:-g>
46
- +) add_subdirectory(abc)
47
- endif()
48
-
49
- ### stefanottili
50
- clang-1400.0.29.202 as part of Xcode 14.1.0 compiles OpenRoad without issues
51
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/2952.md DELETED
@@ -1,104 +0,0 @@
1
- # Cannot build with CUDA
2
-
3
- Tool: Verilog to DB
4
-
5
- Subcategory: Compiler version mismatch
6
-
7
- ## Conversation
8
-
9
- ### yathAg
10
- I am trying to build Openroad with cmake .. -DGPU=true and I get the following output
11
-
12
- ```
13
- -- GPU is enabled
14
- -- CUDA is found
15
- -- The CUDA compiler identification is NVIDIA 10.1.243
16
- -- Detecting CUDA compiler ABI info
17
- -- Detecting CUDA compiler ABI info - done
18
- -- Check for working CUDA compiler: /usr/bin/nvcc - skipped
19
- -- Detecting CUDA compile features
20
- -- Detecting CUDA compile features - done
21
- -- Found re2: /opt/or-tools/lib/cmake/re2/re2Config.cmake (found version "9.0.0")
22
- -- Found Clp: /opt/or-tools/lib/cmake/Clp/ClpConfig.cmake (found version "1.17.7")
23
- -- Found Cbc: /opt/or-tools/lib/cmake/Cbc/CbcConfig.cmake (found version "2.10.7")
24
- -- Found Eigen3: /usr/local/share/eigen3/cmake/Eigen3Config.cmake (found version "3.4.0")
25
- -- Found SCIP: /opt/or-tools/lib/cmake/scip/scip-config.cmake (found version "8.0.1")
26
- -- GUI is enabled
27
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization
28
- -- Found OpenMP_CXX: -fopenmp (found version "4.5")
29
- -- Found OpenMP: TRUE (found version "4.5")
30
- -- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS)
31
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found suitable version "1.80.0", minimum required is "1.78")
32
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization system thread
33
- -- TCL readline enabled
34
- -- Tcl Extended disabled
35
- -- Python3 enabled
36
- -- Configuring done
37
- CMake Warning (dev) in src/gpl/CMakeLists.txt:
38
- Policy CMP0104 is not set: CMAKE_CUDA_ARCHITECTURES now detected for NVCC,
39
- empty CUDA_ARCHITECTURES not allowed. Run "cmake --help-policy CMP0104"
40
- for policy details. Use the cmake_policy command to set the policy and
41
- suppress this warning.
42
-
43
- CUDA_ARCHITECTURES is empty for target "gpl".
44
- This warning is for project developers. Use -Wno-dev to suppress it.
45
-
46
- CMake Error in src/gpl/CMakeLists.txt:
47
- Target "gpl" requires the language dialect "CUDA17" . But the current
48
- compiler "NVIDIA" does not support this, or CMake does not know the flags
49
- to enable it.
50
-
51
-
52
- -- Generating done
53
- CMake Generate step failed. Build files cannot be regenerated correctly.
54
- ```
55
-
56
- I have Cuda installed and on `nvidia-smi` I get
57
-
58
- ```
59
- +-----------------------------------------------------------------------------+
60
- | NVIDIA-SMI 525.85.12 Driver Version: 525.85.12 CUDA Version: 12.0 |
61
- |-------------------------------+----------------------+----------------------+
62
- | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
63
- | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
64
- | | | MIG M. |
65
- |===============================+======================+======================|
66
- | 0 NVIDIA GeForce ... On | 00000000:01:00.0 On | N/A |
67
- | N/A 51C P5 18W / 115W | 187MiB / 6144MiB | 19% Default |
68
- | | | N/A |
69
- +-------------------------------+----------------------+----------------------+
70
-
71
- +-----------------------------------------------------------------------------+
72
- | Processes: |
73
- | GPU GI CI PID Type Process name GPU Memory |
74
- | ID ID Usage |
75
- |=============================================================================|
76
- | 0 N/A N/A 1211 G /usr/lib/xorg/Xorg 52MiB |
77
- | 0 N/A N/A 1875 G /usr/lib/xorg/Xorg 133MiB |
78
- +-----------------------------------------------------------------------------+
79
- ```
80
-
81
- and on `nvcc -V`
82
-
83
- ```
84
- nvcc: NVIDIA (R) Cuda compiler driver
85
- Copyright (c) 2005-2019 NVIDIA Corporation
86
- Built on Sun_Jul_28_19:07:16_PDT_2019
87
- Cuda compilation tools, release 10.1, V10.1.243
88
- ```
89
- Any help on how to get the setup working is really appreciated and thanks in advanced.
90
-
91
-
92
-
93
-
94
-
95
-
96
-
97
- ### vvbandeira
98
- 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).
99
-
100
- ### maliberty
101
- 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.
102
-
103
- FYI - the use of CUDA is quite minimal and probably not worth the bother at this point.
104
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3094.md DELETED
@@ -1,50 +0,0 @@
1
- # Problems with etc/DependencyInstaller.sh and md5 on boost
2
-
3
- Subcategory: Dependency installation
4
-
5
- ## Conversation
6
-
7
- ### oharboe
8
- What's going on here?
9
-
10
- ```bash
11
- $ etc/DependencyInstaller.sh -prefix=~/openroad-tools/ -common
12
- [deleted]
13
- Length: 136670223 (130M) [application/x-gzip]
14
- Saving to: ‘boost_1_80_0.tar.gz.1’
15
-
16
- boost_1_80_0.tar.gz 100%[===================>] 130,34M 2,37MB/s in 65s
17
-
18
- 2023-03-27 16:56:06 (2,02 MB/s) - ‘boost_1_80_0.tar.gz.1’ saved [136670223/136670223]
19
-
20
- + md5sum -c /dev/fd/63
21
- ++ echo '077f074743ea7b0cb49c6ed43953ae95 boost_1_80_0.tar.gz'
22
- boost_1_80_0.tar.gz: FAILED
23
- md5sum: WARNING: 1 computed checksum did NOT match
24
- + exit 1
25
- ```
26
-
27
- ### oharboe
28
- Hmm.... I suspect a manifestation of https://github.com/The-OpenROAD-Project/OpenROAD/issues/3096
29
-
30
- ### vvbandeira
31
- The problem is that the first download failed, and the file was not correctly deleted.
32
-
33
- New download:
34
- ```
35
- boost_1_80_0.tar.gz 100%[===================>] 130,34M 2,37MB/s in 65s
36
- ```
37
-
38
- Saving with the `.1` suffix:
39
- ```
40
- 2023-03-27 16:56:06 (2,02 MB/s) - ‘boost_1_80_0.tar.gz.1’ saved [136670223/136670223]
41
- ```
42
-
43
- Checking against the file without the suffix:
44
- ```
45
- + md5sum -c /dev/fd/63
46
- ++ echo '077f074743ea7b0cb49c6ed43953ae95 boost_1_80_0.tar.gz'
47
- ```
48
-
49
- 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.
50
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3124.md DELETED
@@ -1,43 +0,0 @@
1
- # Problems building - undefined reference to `ord::getLogger()'
2
-
3
- Subcategory: Compilation error
4
-
5
- ## Conversation
6
-
7
- ### oharboe
8
- Any idea what is going on here?
9
-
10
- ```
11
- ./build_openroad.sh --local --openroad-args "-D CMAKE_BUILD_TYPE=RELEASE"
12
- [deleted]
13
- TIMEOUT=5 -D TEST_XML_OUTPUT_DIR= -P /home/oyvind/ascenium/OpenROAD-flow-scripts/dependencies/share/cmake-3.24/Modules/GoogleTestAddTests.cmake
14
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::report(char const*)':
15
- LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
16
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::open_metrics(char const*)':
17
- LoggerCommon.cpp:(.text+0x2e9): undefined reference to `ord::getLogger()'
18
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::close_metrics(char const*)':
19
- LoggerCommon.cpp:(.text+0x309): undefined reference to `ord::getLogger()'
20
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::set_metrics_stage(char const*)':
21
- LoggerCommon.cpp:(.text+0x32e): undefined reference to `ord::getLogger()'
22
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::clear_metrics_stage()':
23
- LoggerCommon.cpp:(.text+0x369): undefined reference to `ord::getLogger()'
24
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o):LoggerCommon.cpp:(.text+0x38e): more undefined references to `ord::getLogger()' follow
25
- collect2: error: ld returned 1 exit status
26
- ```
27
-
28
- ### vijayank88
29
- @oharboe
30
- Have you removed `OpenROAD-flow-scripts/tools` directory before building again.
31
- Sometimes it may cause the issue.
32
- @vvbandeira Can please check this?
33
-
34
- ### maliberty
35
- which binary is it building when the error happens?
36
-
37
- ### oharboe
38
- Rejoice! I finally got it to compile. I deleted the *entire* ORFS folder, recloned, reran sudo ./setup.sh and then the build worked.
39
-
40
- So, somewhere inside the ORFS folder there was an out of date file that wasn't being built...
41
-
42
- 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?
43
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3148.md DELETED
@@ -1,51 +0,0 @@
1
- # LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
2
-
3
- Subcategory: Linking error
4
-
5
- ## Conversation
6
-
7
- ### oharboe
8
- I'm getting this problem again while building OpenROAD locally. I've tried recloning and deleting the entire ORFS folder, still no luck.
9
-
10
- Any ideas?
11
-
12
- ```
13
- $ lsb_release -a
14
- No LSB modules are available.
15
- Distributor ID: Ubuntu
16
- Description: Ubuntu 22.10
17
- Release: 22.10
18
- Codename: kinetic
19
-
20
- ```
21
- ```
22
- ./build_openroad.sh --local --openroad-args "-D CMAKE_BUILD_TYPE=RELEASE"
23
- ```
24
-
25
- ```
26
- [deleted]
27
- 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
28
- : && /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
29
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::report(char const*)':
30
- LoggerCommon.cpp:(.text+0x18f): undefined reference to `ord::getLogger()'
31
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::open_metrics(char const*)':
32
- LoggerCommon.cpp:(.text+0x2e9): undefined reference to `ord::getLogger()'
33
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::close_metrics(char const*)':
34
- LoggerCommon.cpp:(.text+0x309): undefined reference to `ord::getLogger()'
35
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::set_metrics_stage(char const*)':
36
- LoggerCommon.cpp:(.text+0x32e): undefined reference to `ord::getLogger()'
37
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o): in function `utl::clear_metrics_stage()':
38
- LoggerCommon.cpp:(.text+0x369): undefined reference to `ord::getLogger()'
39
- /usr/bin/ld: src/utl/utl.a(LoggerCommon.cpp.o):LoggerCommon.cpp:(.text+0x38e): more undefined references to `ord::getLogger()' follow
40
- collect2: error: ld returned 1 exit status
41
- [3/39] Automatic MOC and UIC for target gui
42
- ninja: build stopped: subcommand failed.
43
- ```
44
-
45
-
46
- ### maliberty
47
- 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.
48
-
49
- ### maliberty
50
- PR coming. I'm not sure why it varies - perhaps different compilers?
51
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3489.md DELETED
@@ -1,26 +0,0 @@
1
- # ABC contains local modifications!
2
-
3
- Tool: Verilog to DB
4
-
5
- Subcategory: Compilation error
6
-
7
- ## Conversation
8
-
9
- ### Simonliudan
10
- [ 12%] Building abc/abc-bafd2a7
11
- Debug: ABCREV=bafd2a7
12
- [ 22%] Building passes/techmap/filterlib.o
13
- [ 22%] Building yosys-smtbmc
14
- ERROR: ABC contains local modifications! Set ABCREV=default in Yosys Makefile!
15
- make: *** [Makefile:749: abc/abc-bafd2a7] Error 1
16
-
17
- in Centos, I have set ABCREV = default, but the debug info is bafd2a7
18
-
19
-
20
- ### vijayank88
21
- Is this installation issue?
22
- Can you provide steps to reproduce the same?
23
-
24
- ### vvbandeira
25
- @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.
26
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3513.md DELETED
@@ -1,33 +0,0 @@
1
- # Build problems. Missing gmock.h
2
-
3
- Subcategory: Missing dependency
4
-
5
- ## Conversation
6
-
7
- ### oharboe
8
- There has been a lot of activity concerning build errors, but I tried with latest master merged with #3512
9
-
10
- Is it enough to update to latest master or do I need to purge something or other locally?
11
-
12
- ```
13
- ./build_openroad.sh --local --openroad-args "-DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_CXX_FLAGS=-g"
14
- ```
15
-
16
- ```
17
- [ 25%] Building CXX object src/odb/test/cpp/CMakeFiles/TestGuide.dir/TestGuide.cpp.o
18
- /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
19
- 13 | #include "gmock/gmock.h"
20
- | ^~~~~~~~~~~~~~~
21
- compilation terminated.
22
- gmake[2]: *** [src/odb/test/cpp/CMakeFiles/OdbGTests.dir/build.make:90: src/odb/test/cpp/CMakeFiles/OdbGTests.dir/TestAbstractLef.cc.o] Error 1
23
- gmake[1]: *** [CMakeFiles/Makefile2:2331: src/odb/test/cpp/CMakeFiles/OdbGTests.dir/all] Error 2
24
- gmake[1]: *** Waiting for unfinished jobs...
25
- ```
26
-
27
-
28
- ### QuantamHD
29
- 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.
30
-
31
- ### vvbandeira
32
- Fixed on #3514
33
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/3779.md DELETED
@@ -1,19 +0,0 @@
1
- # arm64 release for Ubuntu
2
-
3
- Subcategory: Cross-platform compilation
4
-
5
- ## Conversation
6
-
7
- ### ilyaext
8
- I'm looking for an arm64 OpenROAD architecture release to install on Linux AWS EC2 arm64.
9
- Can anyone give me a link or suggest how to compile?
10
-
11
- ### maliberty
12
- We don't test or release on arm64 but you can probably build from source.
13
-
14
- ### maliberty
15
- https://openroad.readthedocs.io/en/latest/user/Build.html
16
-
17
- ### maliberty
18
- https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildLocally.html for ORFS
19
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/4137.md DELETED
@@ -1,1565 +0,0 @@
1
- # OpenROAD build issue
2
-
3
- Subcategory: Compilation error
4
-
5
- ## Conversation
6
-
7
- ### idokoike
8
-
9
- I've been trying to fully install OpenROAD using the` ./build_openroad.sh --local --threads 1` command but I keep getting the error
10
- ```
11
- [INFO FLW-0027] Saving logs to build_openroad.log
12
- [INFO FLW-0028] ./build_openroad.sh --local --threads 1
13
- [INFO FLW-0002] Updating git submodules.
14
- [INFO FLW-0001] Using local build method. This will create binaries at 'tools/install' unless overwritten.
15
- [INFO FLW-0017] Compiling Yosys.
16
- make: Entering directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
17
- mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
18
- cp yosys yosys-config yosys-abc yosys-filterlib yosys-smtbmc /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
19
- strip -S /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys
20
- strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-abc
21
- strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-filterlib
22
- mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys
23
- cp -r share/. /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys/.
24
- make: Leaving directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
25
- [INFO FLW-0018] Compiling OpenROAD.
26
- -- OpenROAD version: v2.0-10669-g436c7801a
27
- -- System name: Linux
28
- -- Compiler: GNU 11.4.0
29
- -- Build type: RELEASE
30
- -- Install prefix: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
31
- -- C++ Standard: 17
32
- -- C++ Standard Required: ON
33
- -- C++ Extensions: OFF
34
- -- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
35
- -- TCL header: /usr/include/tcl/tcl.h
36
- -- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
37
- -- TCL readline header: /usr/include/x86_64-linux-gnu
38
- -- boost: 1.74.0
39
- -- spdlog: 1.9.2
40
- CMake Warning at src/CMakeLists.txt:242 (message):
41
- spdlog: SPDLOG_FMT_EXTERNAL=ON
42
-
43
-
44
- -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
45
- -- STA version: 2.4.0
46
- -- STA git sha: 44f06c521560e803859218732255b3259de048e1
47
- -- System name: Linux
48
- -- Compiler: GNU 11.4.0
49
- -- Build type: RELEASE
50
- -- Build CXX_FLAGS: -O3 -DNDEBUG
51
- -- Install prefix: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
52
- -- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
53
- -- TCL header: /usr/include/tcl/tcl.h
54
- -- SSTA: 0
55
- -- STA executable: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/OpenROAD/src/sta/app/sta
56
- CMake Error at src/gpl/CMakeLists.txt:44 (find_package):
57
- By not providing "Findortools.cmake" in CMAKE_MODULE_PATH this project has
58
- asked CMake to find a package configuration file provided by "ortools", but
59
- CMake did not find one.
60
-
61
- Could not find a package configuration file provided by "ortools" with any
62
- of the following names:
63
-
64
- ortoolsConfig.cmake
65
- ortools-config.cmake
66
-
67
- Add the installation prefix of "ortools" to CMAKE_PREFIX_PATH or set
68
- "ortools_DIR" to a directory containing one of the above files. If
69
- "ortools" provides a separate development package or SDK, be sure it has
70
- been installed.
71
-
72
-
73
- -- Configuring incomplete, errors occurred!
74
-
75
- ```
76
- I've installed or-tools using `git clone https://github.com/google/or-tools.git` and I'm still getting the error
77
-
78
- ### rovinski
79
- This is better to submit as an issue in order to get a better handle on your environment.
80
-
81
- 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.
82
-
83
- ### idokoike
84
- 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
85
-
86
- ```
87
- [INFO FLW-0027] Saving logs to build_openroad.log
88
- [INFO FLW-0028] ./build_openroad.sh --local threads 2 --openroad-args /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build
89
- [INFO FLW-0002] Updating git submodules.
90
- [INFO FLW-0001] Using local build method. This will create binaries at 'tools/install' unless overwritten.
91
- [INFO FLW-0017] Compiling Yosys.
92
- make: Entering directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
93
- mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
94
- cp yosys yosys-config yosys-abc yosys-filterlib yosys-smtbmc /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin
95
- strip -S /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys
96
- strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-abc
97
- strip /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-filterlib
98
- mkdir -p /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys
99
- cp -r share/. /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/yosys/share/yosys/.
100
- make: Leaving directory '/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/yosys'
101
- [INFO FLW-0018] Compiling OpenROAD.
102
- -- ortools version: 9.7.3002
103
- -- Build type: Release
104
- -- Build C++ library: ON
105
- -- Build Python: OFF
106
- -- Build Java: OFF
107
- -- Build .Net: OFF
108
- -- Build Flatzinc: ON
109
- -- Build LP Parser: ON
110
- -- Build standalone Glop: OFF
111
- -- Build samples: ON
112
- -- Build C++ samples: ON
113
- -- Build Python samples: OFF
114
- -- Build Java samples: OFF
115
- -- Build .Net samples: OFF
116
- -- Build examples: ON
117
- -- Build C++ examples: ON
118
- -- Build Python examples: OFF
119
- -- Build Java examples: OFF
120
- -- Build .Net examples: OFF
121
- -- Build documentation: OFF
122
- -- Install doc: OFF
123
- -- Build all dependencies: ON
124
- -- Build ZLIB: ON
125
- -- Build abseil-cpp: ON
126
- -- Build protobuf: ON
127
- -- Build re2: ON
128
- -- Build googletest: ON
129
- -- COIN-OR support: OFF
130
- -- GLPK support: OFF
131
- -- HiGHS support: OFF
132
- -- PDLP support: ON
133
- -- Build PDLP: ON
134
- -- Build eigen3: ON
135
- -- SCIP support: OFF
136
- -- CPLEX support: OFF
137
- -- XPRESS support: OFF
138
- -- C++: Build doc: OFF
139
- -- Fetching ZLIB
140
- -- Populating zlib
141
- -- Configuring done
142
- -- Generating done
143
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/zlib-subbuild
144
- [100%] Built target zlib-populate
145
- -- Fetching ZLIB - fetched
146
- -- Fetching Abseil-cpp
147
- -- Populating absl
148
- -- Configuring done
149
- -- Generating done
150
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/absl-subbuild
151
- [100%] Built target absl-populate
152
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:605 (message):
153
- ABSL_CXX_STANDARD:
154
- Call Stack (most recent call first):
155
- build/_deps/absl-src/CMakeLists.txt:86 (include)
156
-
157
-
158
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:606 (message):
159
- CMAKE_CXX_STANDARD: 17
160
- Call Stack (most recent call first):
161
- build/_deps/absl-src/CMakeLists.txt:86 (include)
162
-
163
-
164
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:607 (message):
165
- CMAKE_CXX_STANDARD_REQUIRED: ON
166
- Call Stack (most recent call first):
167
- build/_deps/absl-src/CMakeLists.txt:86 (include)
168
-
169
-
170
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:608 (message):
171
- CMAKE_CXX_FLAGS:
172
- Call Stack (most recent call first):
173
- build/_deps/absl-src/CMakeLists.txt:86 (include)
174
-
175
-
176
- CMake Warning at build/_deps/absl-src/absl/copts/AbseilConfigureCopts.cmake:97 (message):
177
- ABSL_CXX_STANDARD: 17.
178
- Call Stack (most recent call first):
179
- build/_deps/absl-src/CMake/AbseilHelpers.cmake:18 (include)
180
- build/_deps/absl-src/CMakeLists.txt:87 (include)
181
-
182
-
183
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:605 (message):
184
- ABSL_CXX_STANDARD: 17
185
- Call Stack (most recent call first):
186
- build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
187
- build/_deps/absl-src/CMakeLists.txt:87 (include)
188
-
189
-
190
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:606 (message):
191
- CMAKE_CXX_STANDARD: 17
192
- Call Stack (most recent call first):
193
- build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
194
- build/_deps/absl-src/CMakeLists.txt:87 (include)
195
-
196
-
197
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:607 (message):
198
- CMAKE_CXX_STANDARD_REQUIRED: ON
199
- Call Stack (most recent call first):
200
- build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
201
- build/_deps/absl-src/CMakeLists.txt:87 (include)
202
-
203
-
204
- CMake Warning at build/_deps/absl-src/CMake/AbseilDll.cmake:608 (message):
205
- CMAKE_CXX_FLAGS:
206
- Call Stack (most recent call first):
207
- build/_deps/absl-src/CMake/AbseilHelpers.cmake:19 (include)
208
- build/_deps/absl-src/CMakeLists.txt:87 (include)
209
-
210
-
211
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
212
- Force CXX_FLAGS flags to cxx_std_17
213
- Call Stack (most recent call first):
214
- build/_deps/absl-src/absl/base/CMakeLists.txt:20 (absl_cc_library)
215
-
216
-
217
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
218
- Force CXX_FLAGS flags to cxx_std_17
219
- Call Stack (most recent call first):
220
- build/_deps/absl-src/absl/base/CMakeLists.txt:33 (absl_cc_library)
221
-
222
-
223
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
224
- Force CXX_FLAGS flags to cxx_std_17
225
- Call Stack (most recent call first):
226
- build/_deps/absl-src/absl/base/CMakeLists.txt:44 (absl_cc_library)
227
-
228
-
229
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
230
- Force CXX_FLAGS flags to cxx_std_17
231
- Call Stack (most recent call first):
232
- build/_deps/absl-src/absl/base/CMakeLists.txt:58 (absl_cc_library)
233
-
234
-
235
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
236
- Force CXX_FLAGS flags to cxx_std_17
237
- Call Stack (most recent call first):
238
- build/_deps/absl-src/absl/base/CMakeLists.txt:76 (absl_cc_library)
239
-
240
-
241
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
242
- Force CXX_FLAGS flags to cxx_std_17
243
- Call Stack (most recent call first):
244
- build/_deps/absl-src/absl/base/CMakeLists.txt:95 (absl_cc_library)
245
-
246
-
247
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
248
- Force CXX_FLAGS flags to cxx_std_17
249
- Call Stack (most recent call first):
250
- build/_deps/absl-src/absl/base/CMakeLists.txt:107 (absl_cc_library)
251
-
252
-
253
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
254
- Force CXX_FLAGS flags to cxx_std_17
255
- Call Stack (most recent call first):
256
- build/_deps/absl-src/absl/base/CMakeLists.txt:121 (absl_cc_library)
257
-
258
-
259
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
260
- Force CXX_FLAGS flags to cxx_std_17
261
- Call Stack (most recent call first):
262
- build/_deps/absl-src/absl/base/CMakeLists.txt:140 (absl_cc_library)
263
-
264
-
265
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
266
- Force CXX_FLAGS flags to cxx_std_17
267
- Call Stack (most recent call first):
268
- build/_deps/absl-src/absl/base/CMakeLists.txt:161 (absl_cc_library)
269
-
270
-
271
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
272
- Force CXX_FLAGS flags to cxx_std_17
273
- Call Stack (most recent call first):
274
- build/_deps/absl-src/absl/base/CMakeLists.txt:177 (absl_cc_library)
275
-
276
-
277
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
278
- Force CXX_FLAGS flags to cxx_std_17
279
- Call Stack (most recent call first):
280
- build/_deps/absl-src/absl/base/CMakeLists.txt:220 (absl_cc_library)
281
-
282
-
283
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
284
- Force CXX_FLAGS flags to cxx_std_17
285
- Call Stack (most recent call first):
286
- build/_deps/absl-src/absl/base/CMakeLists.txt:249 (absl_cc_library)
287
-
288
-
289
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
290
- Force CXX_FLAGS flags to cxx_std_17
291
- Call Stack (most recent call first):
292
- build/_deps/absl-src/absl/base/CMakeLists.txt:428 (absl_cc_library)
293
-
294
-
295
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
296
- Force CXX_FLAGS flags to cxx_std_17
297
- Call Stack (most recent call first):
298
- build/_deps/absl-src/absl/base/CMakeLists.txt:539 (absl_cc_library)
299
-
300
-
301
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
302
- Force CXX_FLAGS flags to cxx_std_17
303
- Call Stack (most recent call first):
304
- build/_deps/absl-src/absl/base/CMakeLists.txt:591 (absl_cc_library)
305
-
306
-
307
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
308
- Force CXX_FLAGS flags to cxx_std_17
309
- Call Stack (most recent call first):
310
- build/_deps/absl-src/absl/base/CMakeLists.txt:623 (absl_cc_library)
311
-
312
-
313
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
314
- Force CXX_FLAGS flags to cxx_std_17
315
- Call Stack (most recent call first):
316
- build/_deps/absl-src/absl/base/CMakeLists.txt:649 (absl_cc_library)
317
-
318
-
319
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
320
- Force CXX_FLAGS flags to cxx_std_17
321
- Call Stack (most recent call first):
322
- build/_deps/absl-src/absl/algorithm/CMakeLists.txt:17 (absl_cc_library)
323
-
324
-
325
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
326
- Force CXX_FLAGS flags to cxx_std_17
327
- Call Stack (most recent call first):
328
- build/_deps/absl-src/absl/algorithm/CMakeLists.txt:42 (absl_cc_library)
329
-
330
-
331
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
332
- Force CXX_FLAGS flags to cxx_std_17
333
- Call Stack (most recent call first):
334
- build/_deps/absl-src/absl/cleanup/CMakeLists.txt:16 (absl_cc_library)
335
-
336
-
337
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
338
- Force CXX_FLAGS flags to cxx_std_17
339
- Call Stack (most recent call first):
340
- build/_deps/absl-src/absl/cleanup/CMakeLists.txt:30 (absl_cc_library)
341
-
342
-
343
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
344
- Force CXX_FLAGS flags to cxx_std_17
345
- Call Stack (most recent call first):
346
- build/_deps/absl-src/absl/container/CMakeLists.txt:17 (absl_cc_library)
347
-
348
-
349
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
350
- Force CXX_FLAGS flags to cxx_std_17
351
- Call Stack (most recent call first):
352
- build/_deps/absl-src/absl/container/CMakeLists.txt:91 (absl_cc_library)
353
-
354
-
355
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
356
- Force CXX_FLAGS flags to cxx_std_17
357
- Call Stack (most recent call first):
358
- build/_deps/absl-src/absl/container/CMakeLists.txt:120 (absl_cc_library)
359
-
360
-
361
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
362
- Force CXX_FLAGS flags to cxx_std_17
363
- Call Stack (most recent call first):
364
- build/_deps/absl-src/absl/container/CMakeLists.txt:170 (absl_cc_library)
365
-
366
-
367
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
368
- Force CXX_FLAGS flags to cxx_std_17
369
- Call Stack (most recent call first):
370
- build/_deps/absl-src/absl/container/CMakeLists.txt:186 (absl_cc_library)
371
-
372
-
373
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
374
- Force CXX_FLAGS flags to cxx_std_17
375
- Call Stack (most recent call first):
376
- build/_deps/absl-src/absl/container/CMakeLists.txt:204 (absl_cc_library)
377
-
378
-
379
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
380
- Force CXX_FLAGS flags to cxx_std_17
381
- Call Stack (most recent call first):
382
- build/_deps/absl-src/absl/container/CMakeLists.txt:277 (absl_cc_library)
383
-
384
-
385
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
386
- Force CXX_FLAGS flags to cxx_std_17
387
- Call Stack (most recent call first):
388
- build/_deps/absl-src/absl/container/CMakeLists.txt:313 (absl_cc_library)
389
-
390
-
391
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
392
- Force CXX_FLAGS flags to cxx_std_17
393
- Call Stack (most recent call first):
394
- build/_deps/absl-src/absl/container/CMakeLists.txt:351 (absl_cc_library)
395
-
396
-
397
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
398
- Force CXX_FLAGS flags to cxx_std_17
399
- Call Stack (most recent call first):
400
- build/_deps/absl-src/absl/container/CMakeLists.txt:387 (absl_cc_library)
401
-
402
-
403
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
404
- Force CXX_FLAGS flags to cxx_std_17
405
- Call Stack (most recent call first):
406
- build/_deps/absl-src/absl/container/CMakeLists.txt:423 (absl_cc_library)
407
-
408
-
409
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
410
- Force CXX_FLAGS flags to cxx_std_17
411
- Call Stack (most recent call first):
412
- build/_deps/absl-src/absl/container/CMakeLists.txt:453 (absl_cc_library)
413
-
414
-
415
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
416
- Force CXX_FLAGS flags to cxx_std_17
417
- Call Stack (most recent call first):
418
- build/_deps/absl-src/absl/container/CMakeLists.txt:530 (absl_cc_library)
419
-
420
-
421
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
422
- Force CXX_FLAGS flags to cxx_std_17
423
- Call Stack (most recent call first):
424
- build/_deps/absl-src/absl/container/CMakeLists.txt:556 (absl_cc_library)
425
-
426
-
427
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
428
- Force CXX_FLAGS flags to cxx_std_17
429
- Call Stack (most recent call first):
430
- build/_deps/absl-src/absl/container/CMakeLists.txt:581 (absl_cc_library)
431
-
432
-
433
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
434
- Force CXX_FLAGS flags to cxx_std_17
435
- Call Stack (most recent call first):
436
- build/_deps/absl-src/absl/container/CMakeLists.txt:613 (absl_cc_library)
437
-
438
-
439
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
440
- Force CXX_FLAGS flags to cxx_std_17
441
- Call Stack (most recent call first):
442
- build/_deps/absl-src/absl/container/CMakeLists.txt:625 (absl_cc_library)
443
-
444
-
445
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
446
- Force CXX_FLAGS flags to cxx_std_17
447
- Call Stack (most recent call first):
448
- build/_deps/absl-src/absl/container/CMakeLists.txt:638 (absl_cc_library)
449
-
450
-
451
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
452
- Force CXX_FLAGS flags to cxx_std_17
453
- Call Stack (most recent call first):
454
- build/_deps/absl-src/absl/container/CMakeLists.txt:664 (absl_cc_library)
455
-
456
-
457
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
458
- Force CXX_FLAGS flags to cxx_std_17
459
- Call Stack (most recent call first):
460
- build/_deps/absl-src/absl/container/CMakeLists.txt:679 (absl_cc_library)
461
-
462
-
463
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
464
- Force CXX_FLAGS flags to cxx_std_17
465
- Call Stack (most recent call first):
466
- build/_deps/absl-src/absl/container/CMakeLists.txt:691 (absl_cc_library)
467
-
468
-
469
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
470
- Force CXX_FLAGS flags to cxx_std_17
471
- Call Stack (most recent call first):
472
- build/_deps/absl-src/absl/container/CMakeLists.txt:760 (absl_cc_library)
473
-
474
-
475
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
476
- Force CXX_FLAGS flags to cxx_std_17
477
- Call Stack (most recent call first):
478
- build/_deps/absl-src/absl/crc/CMakeLists.txt:16 (absl_cc_library)
479
-
480
-
481
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
482
- Force CXX_FLAGS flags to cxx_std_17
483
- Call Stack (most recent call first):
484
- build/_deps/absl-src/absl/crc/CMakeLists.txt:31 (absl_cc_library)
485
-
486
-
487
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
488
- Force CXX_FLAGS flags to cxx_std_17
489
- Call Stack (most recent call first):
490
- build/_deps/absl-src/absl/crc/CMakeLists.txt:56 (absl_cc_library)
491
-
492
-
493
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
494
- Force CXX_FLAGS flags to cxx_std_17
495
- Call Stack (most recent call first):
496
- build/_deps/absl-src/absl/crc/CMakeLists.txt:97 (absl_cc_library)
497
-
498
-
499
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
500
- Force CXX_FLAGS flags to cxx_std_17
501
- Call Stack (most recent call first):
502
- build/_deps/absl-src/absl/crc/CMakeLists.txt:109 (absl_cc_library)
503
-
504
-
505
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
506
- Force CXX_FLAGS flags to cxx_std_17
507
- Call Stack (most recent call first):
508
- build/_deps/absl-src/absl/crc/CMakeLists.txt:150 (absl_cc_library)
509
-
510
-
511
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
512
- Force CXX_FLAGS flags to cxx_std_17
513
- Call Stack (most recent call first):
514
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:19 (absl_cc_library)
515
-
516
-
517
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
518
- Force CXX_FLAGS flags to cxx_std_17
519
- Call Stack (most recent call first):
520
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:61 (absl_cc_library)
521
-
522
-
523
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
524
- Force CXX_FLAGS flags to cxx_std_17
525
- Call Stack (most recent call first):
526
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:115 (absl_cc_library)
527
-
528
-
529
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
530
- Force CXX_FLAGS flags to cxx_std_17
531
- Call Stack (most recent call first):
532
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:132 (absl_cc_library)
533
-
534
-
535
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
536
- Force CXX_FLAGS flags to cxx_std_17
537
- Call Stack (most recent call first):
538
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:169 (absl_cc_library)
539
-
540
-
541
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
542
- Force CXX_FLAGS flags to cxx_std_17
543
- Call Stack (most recent call first):
544
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:191 (absl_cc_library)
545
-
546
-
547
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
548
- Force CXX_FLAGS flags to cxx_std_17
549
- Call Stack (most recent call first):
550
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:223 (absl_cc_library)
551
-
552
-
553
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
554
- Force CXX_FLAGS flags to cxx_std_17
555
- Call Stack (most recent call first):
556
- build/_deps/absl-src/absl/debugging/CMakeLists.txt:285 (absl_cc_library)
557
-
558
-
559
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
560
- Force CXX_FLAGS flags to cxx_std_17
561
- Call Stack (most recent call first):
562
- build/_deps/absl-src/absl/flags/CMakeLists.txt:18 (absl_cc_library)
563
-
564
-
565
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
566
- Force CXX_FLAGS flags to cxx_std_17
567
- Call Stack (most recent call first):
568
- build/_deps/absl-src/absl/flags/CMakeLists.txt:34 (absl_cc_library)
569
-
570
-
571
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
572
- Force CXX_FLAGS flags to cxx_std_17
573
- Call Stack (most recent call first):
574
- build/_deps/absl-src/absl/flags/CMakeLists.txt:54 (absl_cc_library)
575
-
576
-
577
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
578
- Force CXX_FLAGS flags to cxx_std_17
579
- Call Stack (most recent call first):
580
- build/_deps/absl-src/absl/flags/CMakeLists.txt:75 (absl_cc_library)
581
-
582
-
583
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
584
- Force CXX_FLAGS flags to cxx_std_17
585
- Call Stack (most recent call first):
586
- build/_deps/absl-src/absl/flags/CMakeLists.txt:96 (absl_cc_library)
587
-
588
-
589
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
590
- Force CXX_FLAGS flags to cxx_std_17
591
- Call Stack (most recent call first):
592
- build/_deps/absl-src/absl/flags/CMakeLists.txt:113 (absl_cc_library)
593
-
594
-
595
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
596
- Force CXX_FLAGS flags to cxx_std_17
597
- Call Stack (most recent call first):
598
- build/_deps/absl-src/absl/flags/CMakeLists.txt:133 (absl_cc_library)
599
-
600
-
601
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
602
- Force CXX_FLAGS flags to cxx_std_17
603
- Call Stack (most recent call first):
604
- build/_deps/absl-src/absl/flags/CMakeLists.txt:151 (absl_cc_library)
605
-
606
-
607
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
608
- Force CXX_FLAGS flags to cxx_std_17
609
- Call Stack (most recent call first):
610
- build/_deps/absl-src/absl/flags/CMakeLists.txt:174 (absl_cc_library)
611
-
612
-
613
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
614
- Force CXX_FLAGS flags to cxx_std_17
615
- Call Stack (most recent call first):
616
- build/_deps/absl-src/absl/flags/CMakeLists.txt:199 (absl_cc_library)
617
-
618
-
619
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
620
- Force CXX_FLAGS flags to cxx_std_17
621
- Call Stack (most recent call first):
622
- build/_deps/absl-src/absl/flags/CMakeLists.txt:224 (absl_cc_library)
623
-
624
-
625
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
626
- Force CXX_FLAGS flags to cxx_std_17
627
- Call Stack (most recent call first):
628
- build/_deps/absl-src/absl/flags/CMakeLists.txt:250 (absl_cc_library)
629
-
630
-
631
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
632
- Force CXX_FLAGS flags to cxx_std_17
633
- Call Stack (most recent call first):
634
- build/_deps/absl-src/absl/flags/CMakeLists.txt:269 (absl_cc_library)
635
-
636
-
637
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
638
- Force CXX_FLAGS flags to cxx_std_17
639
- Call Stack (most recent call first):
640
- build/_deps/absl-src/absl/functional/CMakeLists.txt:17 (absl_cc_library)
641
-
642
-
643
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
644
- Force CXX_FLAGS flags to cxx_std_17
645
- Call Stack (most recent call first):
646
- build/_deps/absl-src/absl/functional/CMakeLists.txt:53 (absl_cc_library)
647
-
648
-
649
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
650
- Force CXX_FLAGS flags to cxx_std_17
651
- Call Stack (most recent call first):
652
- build/_deps/absl-src/absl/functional/CMakeLists.txt:81 (absl_cc_library)
653
-
654
-
655
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
656
- Force CXX_FLAGS flags to cxx_std_17
657
- Call Stack (most recent call first):
658
- build/_deps/absl-src/absl/hash/CMakeLists.txt:17 (absl_cc_library)
659
-
660
-
661
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
662
- Force CXX_FLAGS flags to cxx_std_17
663
- Call Stack (most recent call first):
664
- build/_deps/absl-src/absl/hash/CMakeLists.txt:106 (absl_cc_library)
665
-
666
-
667
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
668
- Force CXX_FLAGS flags to cxx_std_17
669
- Call Stack (most recent call first):
670
- build/_deps/absl-src/absl/hash/CMakeLists.txt:134 (absl_cc_library)
671
-
672
-
673
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
674
- Force CXX_FLAGS flags to cxx_std_17
675
- Call Stack (most recent call first):
676
- build/_deps/absl-src/absl/log/CMakeLists.txt:18 (absl_cc_library)
677
-
678
-
679
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
680
- Force CXX_FLAGS flags to cxx_std_17
681
- Call Stack (most recent call first):
682
- build/_deps/absl-src/absl/log/CMakeLists.txt:36 (absl_cc_library)
683
-
684
-
685
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
686
- Force CXX_FLAGS flags to cxx_std_17
687
- Call Stack (most recent call first):
688
- build/_deps/absl-src/absl/log/CMakeLists.txt:56 (absl_cc_library)
689
-
690
-
691
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
692
- Force CXX_FLAGS flags to cxx_std_17
693
- Call Stack (most recent call first):
694
- build/_deps/absl-src/absl/log/CMakeLists.txt:74 (absl_cc_library)
695
-
696
-
697
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
698
- Force CXX_FLAGS flags to cxx_std_17
699
- Call Stack (most recent call first):
700
- build/_deps/absl-src/absl/log/CMakeLists.txt:89 (absl_cc_library)
701
-
702
-
703
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
704
- Force CXX_FLAGS flags to cxx_std_17
705
- Call Stack (most recent call first):
706
- build/_deps/absl-src/absl/log/CMakeLists.txt:103 (absl_cc_library)
707
-
708
-
709
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
710
- Force CXX_FLAGS flags to cxx_std_17
711
- Call Stack (most recent call first):
712
- build/_deps/absl-src/absl/log/CMakeLists.txt:127 (absl_cc_library)
713
-
714
-
715
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
716
- Force CXX_FLAGS flags to cxx_std_17
717
- Call Stack (most recent call first):
718
- build/_deps/absl-src/absl/log/CMakeLists.txt:147 (absl_cc_library)
719
-
720
-
721
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
722
- Force CXX_FLAGS flags to cxx_std_17
723
- Call Stack (most recent call first):
724
- build/_deps/absl-src/absl/log/CMakeLists.txt:163 (absl_cc_library)
725
-
726
-
727
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
728
- Force CXX_FLAGS flags to cxx_std_17
729
- Call Stack (most recent call first):
730
- build/_deps/absl-src/absl/log/CMakeLists.txt:182 (absl_cc_library)
731
-
732
-
733
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
734
- Force CXX_FLAGS flags to cxx_std_17
735
- Call Stack (most recent call first):
736
- build/_deps/absl-src/absl/log/CMakeLists.txt:219 (absl_cc_library)
737
-
738
-
739
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
740
- Force CXX_FLAGS flags to cxx_std_17
741
- Call Stack (most recent call first):
742
- build/_deps/absl-src/absl/log/CMakeLists.txt:248 (absl_cc_library)
743
-
744
-
745
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
746
- Force CXX_FLAGS flags to cxx_std_17
747
- Call Stack (most recent call first):
748
- build/_deps/absl-src/absl/log/CMakeLists.txt:264 (absl_cc_library)
749
-
750
-
751
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
752
- Force CXX_FLAGS flags to cxx_std_17
753
- Call Stack (most recent call first):
754
- build/_deps/absl-src/absl/log/CMakeLists.txt:281 (absl_cc_library)
755
-
756
-
757
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
758
- Force CXX_FLAGS flags to cxx_std_17
759
- Call Stack (most recent call first):
760
- build/_deps/absl-src/absl/log/CMakeLists.txt:363 (absl_cc_library)
761
-
762
-
763
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
764
- Force CXX_FLAGS flags to cxx_std_17
765
- Call Stack (most recent call first):
766
- build/_deps/absl-src/absl/log/CMakeLists.txt:377 (absl_cc_library)
767
-
768
-
769
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
770
- Force CXX_FLAGS flags to cxx_std_17
771
- Call Stack (most recent call first):
772
- build/_deps/absl-src/absl/log/CMakeLists.txt:394 (absl_cc_library)
773
-
774
-
775
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
776
- Force CXX_FLAGS flags to cxx_std_17
777
- Call Stack (most recent call first):
778
- build/_deps/absl-src/absl/log/CMakeLists.txt:409 (absl_cc_library)
779
-
780
-
781
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
782
- Force CXX_FLAGS flags to cxx_std_17
783
- Call Stack (most recent call first):
784
- build/_deps/absl-src/absl/log/CMakeLists.txt:424 (absl_cc_library)
785
-
786
-
787
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
788
- Force CXX_FLAGS flags to cxx_std_17
789
- Call Stack (most recent call first):
790
- build/_deps/absl-src/absl/log/CMakeLists.txt:444 (absl_cc_library)
791
-
792
-
793
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
794
- Force CXX_FLAGS flags to cxx_std_17
795
- Call Stack (most recent call first):
796
- build/_deps/absl-src/absl/log/CMakeLists.txt:463 (absl_cc_library)
797
-
798
-
799
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
800
- Force CXX_FLAGS flags to cxx_std_17
801
- Call Stack (most recent call first):
802
- build/_deps/absl-src/absl/log/CMakeLists.txt:487 (absl_cc_library)
803
-
804
-
805
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
806
- Force CXX_FLAGS flags to cxx_std_17
807
- Call Stack (most recent call first):
808
- build/_deps/absl-src/absl/log/CMakeLists.txt:507 (absl_cc_library)
809
-
810
-
811
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
812
- Force CXX_FLAGS flags to cxx_std_17
813
- Call Stack (most recent call first):
814
- build/_deps/absl-src/absl/log/CMakeLists.txt:526 (absl_cc_library)
815
-
816
-
817
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
818
- Force CXX_FLAGS flags to cxx_std_17
819
- Call Stack (most recent call first):
820
- build/_deps/absl-src/absl/log/CMakeLists.txt:541 (absl_cc_library)
821
-
822
-
823
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
824
- Force CXX_FLAGS flags to cxx_std_17
825
- Call Stack (most recent call first):
826
- build/_deps/absl-src/absl/log/CMakeLists.txt:563 (absl_cc_library)
827
-
828
-
829
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
830
- Force CXX_FLAGS flags to cxx_std_17
831
- Call Stack (most recent call first):
832
- build/_deps/absl-src/absl/log/CMakeLists.txt:580 (absl_cc_library)
833
-
834
-
835
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
836
- Force CXX_FLAGS flags to cxx_std_17
837
- Call Stack (most recent call first):
838
- build/_deps/absl-src/absl/log/CMakeLists.txt:597 (absl_cc_library)
839
-
840
-
841
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
842
- Force CXX_FLAGS flags to cxx_std_17
843
- Call Stack (most recent call first):
844
- build/_deps/absl-src/absl/log/CMakeLists.txt:643 (absl_cc_library)
845
-
846
-
847
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
848
- Force CXX_FLAGS flags to cxx_std_17
849
- Call Stack (most recent call first):
850
- build/_deps/absl-src/absl/log/CMakeLists.txt:658 (absl_cc_library)
851
-
852
-
853
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
854
- Force CXX_FLAGS flags to cxx_std_17
855
- Call Stack (most recent call first):
856
- build/_deps/absl-src/absl/memory/CMakeLists.txt:17 (absl_cc_library)
857
-
858
-
859
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
860
- Force CXX_FLAGS flags to cxx_std_17
861
- Call Stack (most recent call first):
862
- build/_deps/absl-src/absl/meta/CMakeLists.txt:17 (absl_cc_library)
863
-
864
-
865
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
866
- Force CXX_FLAGS flags to cxx_std_17
867
- Call Stack (most recent call first):
868
- build/_deps/absl-src/absl/meta/CMakeLists.txt:45 (absl_cc_library)
869
-
870
-
871
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
872
- Force CXX_FLAGS flags to cxx_std_17
873
- Call Stack (most recent call first):
874
- build/_deps/absl-src/absl/numeric/CMakeLists.txt:17 (absl_cc_library)
875
-
876
-
877
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
878
- Force CXX_FLAGS flags to cxx_std_17
879
- Call Stack (most recent call first):
880
- build/_deps/absl-src/absl/numeric/CMakeLists.txt:44 (absl_cc_library)
881
-
882
-
883
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
884
- Force CXX_FLAGS flags to cxx_std_17
885
- Call Stack (most recent call first):
886
- build/_deps/absl-src/absl/numeric/CMakeLists.txt:79 (absl_cc_library)
887
-
888
-
889
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
890
- Force CXX_FLAGS flags to cxx_std_17
891
- Call Stack (most recent call first):
892
- build/_deps/absl-src/absl/numeric/CMakeLists.txt:89 (absl_cc_library)
893
-
894
-
895
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
896
- Force CXX_FLAGS flags to cxx_std_17
897
- Call Stack (most recent call first):
898
- build/_deps/absl-src/absl/profiling/CMakeLists.txt:15 (absl_cc_library)
899
-
900
-
901
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
902
- Force CXX_FLAGS flags to cxx_std_17
903
- Call Stack (most recent call first):
904
- build/_deps/absl-src/absl/profiling/CMakeLists.txt:40 (absl_cc_library)
905
-
906
-
907
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
908
- Force CXX_FLAGS flags to cxx_std_17
909
- Call Stack (most recent call first):
910
- build/_deps/absl-src/absl/profiling/CMakeLists.txt:67 (absl_cc_library)
911
-
912
-
913
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
914
- Force CXX_FLAGS flags to cxx_std_17
915
- Call Stack (most recent call first):
916
- build/_deps/absl-src/absl/random/CMakeLists.txt:17 (absl_cc_library)
917
-
918
-
919
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
920
- Force CXX_FLAGS flags to cxx_std_17
921
- Call Stack (most recent call first):
922
- build/_deps/absl-src/absl/random/CMakeLists.txt:35 (absl_cc_library)
923
-
924
-
925
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
926
- Force CXX_FLAGS flags to cxx_std_17
927
- Call Stack (most recent call first):
928
- build/_deps/absl-src/absl/random/CMakeLists.txt:70 (absl_cc_library)
929
-
930
-
931
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
932
- Force CXX_FLAGS flags to cxx_std_17
933
- Call Stack (most recent call first):
934
- build/_deps/absl-src/absl/random/CMakeLists.txt:161 (absl_cc_library)
935
-
936
-
937
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
938
- Force CXX_FLAGS flags to cxx_std_17
939
- Call Stack (most recent call first):
940
- build/_deps/absl-src/absl/random/CMakeLists.txt:199 (absl_cc_library)
941
-
942
-
943
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
944
- Force CXX_FLAGS flags to cxx_std_17
945
- Call Stack (most recent call first):
946
- build/_deps/absl-src/absl/random/CMakeLists.txt:214 (absl_cc_library)
947
-
948
-
949
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
950
- Force CXX_FLAGS flags to cxx_std_17
951
- Call Stack (most recent call first):
952
- build/_deps/absl-src/absl/random/CMakeLists.txt:517 (absl_cc_library)
953
-
954
-
955
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
956
- Force CXX_FLAGS flags to cxx_std_17
957
- Call Stack (most recent call first):
958
- build/_deps/absl-src/absl/random/CMakeLists.txt:531 (absl_cc_library)
959
-
960
-
961
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
962
- Force CXX_FLAGS flags to cxx_std_17
963
- Call Stack (most recent call first):
964
- build/_deps/absl-src/absl/random/CMakeLists.txt:547 (absl_cc_library)
965
-
966
-
967
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
968
- Force CXX_FLAGS flags to cxx_std_17
969
- Call Stack (most recent call first):
970
- build/_deps/absl-src/absl/random/CMakeLists.txt:561 (absl_cc_library)
971
-
972
-
973
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
974
- Force CXX_FLAGS flags to cxx_std_17
975
- Call Stack (most recent call first):
976
- build/_deps/absl-src/absl/random/CMakeLists.txt:583 (absl_cc_library)
977
-
978
-
979
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
980
- Force CXX_FLAGS flags to cxx_std_17
981
- Call Stack (most recent call first):
982
- build/_deps/absl-src/absl/random/CMakeLists.txt:639 (absl_cc_library)
983
-
984
-
985
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
986
- Force CXX_FLAGS flags to cxx_std_17
987
- Call Stack (most recent call first):
988
- build/_deps/absl-src/absl/random/CMakeLists.txt:657 (absl_cc_library)
989
-
990
-
991
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
992
- Force CXX_FLAGS flags to cxx_std_17
993
- Call Stack (most recent call first):
994
- build/_deps/absl-src/absl/random/CMakeLists.txt:672 (absl_cc_library)
995
-
996
-
997
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
998
- Force CXX_FLAGS flags to cxx_std_17
999
- Call Stack (most recent call first):
1000
- build/_deps/absl-src/absl/random/CMakeLists.txt:689 (absl_cc_library)
1001
-
1002
-
1003
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1004
- Force CXX_FLAGS flags to cxx_std_17
1005
- Call Stack (most recent call first):
1006
- build/_deps/absl-src/absl/random/CMakeLists.txt:705 (absl_cc_library)
1007
-
1008
-
1009
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1010
- Force CXX_FLAGS flags to cxx_std_17
1011
- Call Stack (most recent call first):
1012
- build/_deps/absl-src/absl/random/CMakeLists.txt:719 (absl_cc_library)
1013
-
1014
-
1015
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1016
- Force CXX_FLAGS flags to cxx_std_17
1017
- Call Stack (most recent call first):
1018
- build/_deps/absl-src/absl/random/CMakeLists.txt:739 (absl_cc_library)
1019
-
1020
-
1021
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1022
- Force CXX_FLAGS flags to cxx_std_17
1023
- Call Stack (most recent call first):
1024
- build/_deps/absl-src/absl/random/CMakeLists.txt:757 (absl_cc_library)
1025
-
1026
-
1027
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1028
- Force CXX_FLAGS flags to cxx_std_17
1029
- Call Stack (most recent call first):
1030
- build/_deps/absl-src/absl/random/CMakeLists.txt:775 (absl_cc_library)
1031
-
1032
-
1033
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1034
- Force CXX_FLAGS flags to cxx_std_17
1035
- Call Stack (most recent call first):
1036
- build/_deps/absl-src/absl/random/CMakeLists.txt:792 (absl_cc_library)
1037
-
1038
-
1039
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1040
- Force CXX_FLAGS flags to cxx_std_17
1041
- Call Stack (most recent call first):
1042
- build/_deps/absl-src/absl/random/CMakeLists.txt:810 (absl_cc_library)
1043
-
1044
-
1045
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1046
- Force CXX_FLAGS flags to cxx_std_17
1047
- Call Stack (most recent call first):
1048
- build/_deps/absl-src/absl/random/CMakeLists.txt:827 (absl_cc_library)
1049
-
1050
-
1051
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1052
- Force CXX_FLAGS flags to cxx_std_17
1053
- Call Stack (most recent call first):
1054
- build/_deps/absl-src/absl/random/CMakeLists.txt:847 (absl_cc_library)
1055
-
1056
-
1057
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1058
- Force CXX_FLAGS flags to cxx_std_17
1059
- Call Stack (most recent call first):
1060
- build/_deps/absl-src/absl/random/CMakeLists.txt:864 (absl_cc_library)
1061
-
1062
-
1063
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1064
- Force CXX_FLAGS flags to cxx_std_17
1065
- Call Stack (most recent call first):
1066
- build/_deps/absl-src/absl/random/CMakeLists.txt:1155 (absl_cc_library)
1067
-
1068
-
1069
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1070
- Force CXX_FLAGS flags to cxx_std_17
1071
- Call Stack (most recent call first):
1072
- build/_deps/absl-src/absl/status/CMakeLists.txt:16 (absl_cc_library)
1073
-
1074
-
1075
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1076
- Force CXX_FLAGS flags to cxx_std_17
1077
- Call Stack (most recent call first):
1078
- build/_deps/absl-src/absl/status/CMakeLists.txt:58 (absl_cc_library)
1079
-
1080
-
1081
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1082
- Force CXX_FLAGS flags to cxx_std_17
1083
- Call Stack (most recent call first):
1084
- build/_deps/absl-src/absl/strings/CMakeLists.txt:17 (absl_cc_library)
1085
-
1086
-
1087
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1088
- Force CXX_FLAGS flags to cxx_std_17
1089
- Call Stack (most recent call first):
1090
- build/_deps/absl-src/absl/strings/CMakeLists.txt:77 (absl_cc_library)
1091
-
1092
-
1093
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1094
- Force CXX_FLAGS flags to cxx_std_17
1095
- Call Stack (most recent call first):
1096
- build/_deps/absl-src/absl/strings/CMakeLists.txt:396 (absl_cc_library)
1097
-
1098
-
1099
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1100
- Force CXX_FLAGS flags to cxx_std_17
1101
- Call Stack (most recent call first):
1102
- build/_deps/absl-src/absl/strings/CMakeLists.txt:409 (absl_cc_library)
1103
-
1104
-
1105
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1106
- Force CXX_FLAGS flags to cxx_std_17
1107
- Call Stack (most recent call first):
1108
- build/_deps/absl-src/absl/strings/CMakeLists.txt:579 (absl_cc_library)
1109
-
1110
-
1111
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1112
- Force CXX_FLAGS flags to cxx_std_17
1113
- Call Stack (most recent call first):
1114
- build/_deps/absl-src/absl/strings/CMakeLists.txt:620 (absl_cc_library)
1115
-
1116
-
1117
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1118
- Force CXX_FLAGS flags to cxx_std_17
1119
- Call Stack (most recent call first):
1120
- build/_deps/absl-src/absl/strings/CMakeLists.txt:647 (absl_cc_library)
1121
-
1122
-
1123
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1124
- Force CXX_FLAGS flags to cxx_std_17
1125
- Call Stack (most recent call first):
1126
- build/_deps/absl-src/absl/strings/CMakeLists.txt:676 (absl_cc_library)
1127
-
1128
-
1129
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1130
- Force CXX_FLAGS flags to cxx_std_17
1131
- Call Stack (most recent call first):
1132
- build/_deps/absl-src/absl/strings/CMakeLists.txt:691 (absl_cc_library)
1133
-
1134
-
1135
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1136
- Force CXX_FLAGS flags to cxx_std_17
1137
- Call Stack (most recent call first):
1138
- build/_deps/absl-src/absl/strings/CMakeLists.txt:725 (absl_cc_library)
1139
-
1140
-
1141
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1142
- Force CXX_FLAGS flags to cxx_std_17
1143
- Call Stack (most recent call first):
1144
- build/_deps/absl-src/absl/strings/CMakeLists.txt:794 (absl_cc_library)
1145
-
1146
-
1147
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1148
- Force CXX_FLAGS flags to cxx_std_17
1149
- Call Stack (most recent call first):
1150
- build/_deps/absl-src/absl/strings/CMakeLists.txt:833 (absl_cc_library)
1151
-
1152
-
1153
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1154
- Force CXX_FLAGS flags to cxx_std_17
1155
- Call Stack (most recent call first):
1156
- build/_deps/absl-src/absl/strings/CMakeLists.txt:866 (absl_cc_library)
1157
-
1158
-
1159
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1160
- Force CXX_FLAGS flags to cxx_std_17
1161
- Call Stack (most recent call first):
1162
- build/_deps/absl-src/absl/synchronization/CMakeLists.txt:18 (absl_cc_library)
1163
-
1164
-
1165
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1166
- Force CXX_FLAGS flags to cxx_std_17
1167
- Call Stack (most recent call first):
1168
- build/_deps/absl-src/absl/synchronization/CMakeLists.txt:37 (absl_cc_library)
1169
-
1170
-
1171
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1172
- Force CXX_FLAGS flags to cxx_std_17
1173
- Call Stack (most recent call first):
1174
- build/_deps/absl-src/absl/synchronization/CMakeLists.txt:50 (absl_cc_library)
1175
-
1176
-
1177
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1178
- Force CXX_FLAGS flags to cxx_std_17
1179
- Call Stack (most recent call first):
1180
- build/_deps/absl-src/absl/time/CMakeLists.txt:17 (absl_cc_library)
1181
-
1182
-
1183
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1184
- Force CXX_FLAGS flags to cxx_std_17
1185
- Call Stack (most recent call first):
1186
- build/_deps/absl-src/absl/time/CMakeLists.txt:45 (absl_cc_library)
1187
-
1188
-
1189
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1190
- Force CXX_FLAGS flags to cxx_std_17
1191
- Call Stack (most recent call first):
1192
- build/_deps/absl-src/absl/time/CMakeLists.txt:61 (absl_cc_library)
1193
-
1194
-
1195
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1196
- Force CXX_FLAGS flags to cxx_std_17
1197
- Call Stack (most recent call first):
1198
- build/_deps/absl-src/absl/types/CMakeLists.txt:16 (absl_cc_library)
1199
-
1200
-
1201
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1202
- Force CXX_FLAGS flags to cxx_std_17
1203
- Call Stack (most recent call first):
1204
- build/_deps/absl-src/absl/types/CMakeLists.txt:33 (absl_cc_library)
1205
-
1206
-
1207
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1208
- Force CXX_FLAGS flags to cxx_std_17
1209
- Call Stack (most recent call first):
1210
- build/_deps/absl-src/absl/types/CMakeLists.txt:47 (absl_cc_library)
1211
-
1212
-
1213
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1214
- Force CXX_FLAGS flags to cxx_std_17
1215
- Call Stack (most recent call first):
1216
- build/_deps/absl-src/absl/types/CMakeLists.txt:106 (absl_cc_library)
1217
-
1218
-
1219
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1220
- Force CXX_FLAGS flags to cxx_std_17
1221
- Call Stack (most recent call first):
1222
- build/_deps/absl-src/absl/types/CMakeLists.txt:163 (absl_cc_library)
1223
-
1224
-
1225
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1226
- Force CXX_FLAGS flags to cxx_std_17
1227
- Call Stack (most recent call first):
1228
- build/_deps/absl-src/absl/types/CMakeLists.txt:183 (absl_cc_library)
1229
-
1230
-
1231
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:293 (message):
1232
- Force CXX_FLAGS flags to cxx_std_17
1233
- Call Stack (most recent call first):
1234
- build/_deps/absl-src/absl/types/CMakeLists.txt:198 (absl_cc_library)
1235
-
1236
-
1237
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1238
- Force CXX_FLAGS flags to cxx_std_17
1239
- Call Stack (most recent call first):
1240
- build/_deps/absl-src/absl/types/CMakeLists.txt:296 (absl_cc_library)
1241
-
1242
-
1243
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1244
- Force CXX_FLAGS flags to cxx_std_17
1245
- Call Stack (most recent call first):
1246
- build/_deps/absl-src/absl/types/CMakeLists.txt:332 (absl_cc_library)
1247
-
1248
-
1249
- CMake Warning at build/_deps/absl-src/CMake/AbseilHelpers.cmake:342 (message):
1250
- Force CXX_FLAGS flags to cxx_std_17
1251
- Call Stack (most recent call first):
1252
- build/_deps/absl-src/absl/utility/CMakeLists.txt:17 (absl_cc_library)
1253
-
1254
-
1255
- -- Fetching Abseil-cpp - fetched
1256
- -- Fetching Protobuf
1257
- -- Populating protobuf
1258
- -- Configuring done
1259
- -- Generating done
1260
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/protobuf-subbuild
1261
- [100%] Built target protobuf-populate
1262
- --
1263
- -- 23.3.0
1264
- -- Fetching Protobuf - fetched
1265
- -- Fetching re2
1266
- -- Populating re2
1267
- -- Configuring done
1268
- -- Generating done
1269
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/re2-subbuild
1270
- [100%] Built target re2-populate
1271
- -- Fetching re2 - fetched
1272
- -- Fetching Eigen3
1273
- -- Populating eigen3
1274
- -- Configuring done
1275
- -- Generating done
1276
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/eigen3-subbuild
1277
- [100%] Built target eigen3-populate
1278
- -- Performing Test COMPILER_SUPPORT_std=cpp03
1279
- -- Performing Test COMPILER_SUPPORT_std=cpp03 - Success
1280
- -- Standard libraries to link to explicitly: none
1281
- -- Found unsuitable Qt version "5.15.3" from /usr/bin/qmake
1282
- -- Qt4 not found, so disabling the mandelbrot and opengl demos
1283
- -- Could NOT find CHOLMOD (missing: CHOLMOD_INCLUDES CHOLMOD_LIBRARIES)
1284
- -- Could NOT find UMFPACK (missing: UMFPACK_INCLUDES UMFPACK_LIBRARIES)
1285
- -- Could NOT find KLU (missing: KLU_INCLUDES KLU_LIBRARIES)
1286
- -- Could NOT find SuperLU (missing: SUPERLU_INCLUDES SUPERLU_LIBRARIES SUPERLU_VERSION_OK) (Required is at least version "4.0")
1287
- -- 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.
1288
- --
1289
- -- Configured Eigen 3.4.0
1290
- --
1291
- -- Available targets (use: make TARGET):
1292
- -- ---------+--------------------------------------------------------------
1293
- -- Target | Description
1294
- -- ---------+--------------------------------------------------------------
1295
- -- install | Install Eigen. Headers will be installed to:
1296
- -- | <CMAKE_INSTALL_PREFIX>/<INCLUDE_INSTALL_DIR>
1297
- -- | Using the following values:
1298
- -- | CMAKE_INSTALL_PREFIX: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/tools/install/OpenROAD
1299
- -- | INCLUDE_INSTALL_DIR: include/eigen3
1300
- -- | Change the install location of Eigen headers using:
1301
- -- | cmake . -DCMAKE_INSTALL_PREFIX=yourprefix
1302
- -- | Or:
1303
- -- | cmake . -DINCLUDE_INSTALL_DIR=yourdir
1304
- -- doc | Generate the API documentation, requires Doxygen & LaTeX
1305
- -- blas | Build BLAS library (not the same thing as Eigen)
1306
- -- uninstall| Remove files installed by the install target
1307
- -- ---------+--------------------------------------------------------------
1308
- --
1309
- -- Fetching Eigen3 - fetched
1310
- -- Fetching googletest
1311
- -- Populating googletest
1312
- -- Configuring done
1313
- -- Generating done
1314
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/googletest-subbuild
1315
- [100%] Built target googletest-populate
1316
- -- Fetching googletest - fetched
1317
- -- Found long size: 8
1318
- -- Found long long size: 8
1319
- -- Found int64_t size: 8
1320
- -- Found unsigned long size: 8
1321
- -- Found unsigned long long size: 8
1322
- -- Found uint64_t size: 8
1323
- -- Found int * size: 8
1324
- -- Adding proto path: $<BUILD_INTERFACE:/home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build/_deps/protobuf-src/src>
1325
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/knapsack.cc: ...
1326
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/knapsack.cc: ...DONE
1327
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/simple_knapsack_program.cc: ...
1328
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/algorithms/samples/simple_knapsack_program.cc: ...DONE
1329
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_linear_sum_assignment.cc: ...
1330
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_linear_sum_assignment.cc: ...DONE
1331
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_min_flow.cc: ...
1332
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/assignment_min_flow.cc: ...DONE
1333
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/balance_min_flow.cc: ...
1334
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/balance_min_flow.cc: ...DONE
1335
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_max_flow_program.cc: ...
1336
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_max_flow_program.cc: ...DONE
1337
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_min_cost_flow_program.cc: ...
1338
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/graph/samples/simple_min_cost_flow_program.cc: ...DONE
1339
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/glop/samples/simple_glop_program.cc: ...
1340
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/glop/samples/simple_glop_program.cc: ...DONE
1341
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/cp_is_fun_cp.cc: ...
1342
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/cp_is_fun_cp.cc: ...DONE
1343
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/minimal_jobshop_cp.cc: ...
1344
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/minimal_jobshop_cp.cc: ...DONE
1345
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nqueens_cp.cc: ...
1346
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nqueens_cp.cc: ...DONE
1347
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nurses_cp.cc: ...
1348
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/nurses_cp.cc: ...DONE
1349
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/rabbits_and_pheasants_cp.cc: ...
1350
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/rabbits_and_pheasants_cp.cc: ...DONE
1351
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_cp_program.cc: ...
1352
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_cp_program.cc: ...DONE
1353
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_ls_program.cc: ...
1354
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_ls_program.cc: ...DONE
1355
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_routing_program.cc: ...
1356
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/simple_routing_program.cc: ...DONE
1357
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp.cc: ...
1358
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp.cc: ...DONE
1359
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_circuit_board.cc: ...
1360
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_circuit_board.cc: ...DONE
1361
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities.cc: ...
1362
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities.cc: ...DONE
1363
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities_routes.cc: ...
1364
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_cities_routes.cc: ...DONE
1365
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_distance_matrix.cc: ...
1366
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/tsp_distance_matrix.cc: ...DONE
1367
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp.cc: ...
1368
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp.cc: ...DONE
1369
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_breaks.cc: ...
1370
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_breaks.cc: ...DONE
1371
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_capacity.cc: ...
1372
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_capacity.cc: ...DONE
1373
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_drop_nodes.cc: ...
1374
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_drop_nodes.cc: ...DONE
1375
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_global_span.cc: ...
1376
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_global_span.cc: ...DONE
1377
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_initial_routes.cc: ...
1378
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_initial_routes.cc: ...DONE
1379
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery.cc: ...
1380
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery.cc: ...DONE
1381
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_fifo.cc: ...
1382
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_fifo.cc: ...DONE
1383
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_lifo.cc: ...
1384
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_pickup_delivery_lifo.cc: ...DONE
1385
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_resources.cc: ...
1386
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_resources.cc: ...DONE
1387
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_routes.cc: ...
1388
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_routes.cc: ...DONE
1389
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_solution_callback.cc: ...
1390
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_solution_callback.cc: ...DONE
1391
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_starts_ends.cc: ...
1392
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_starts_ends.cc: ...DONE
1393
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_time_windows.cc: ...
1394
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_time_windows.cc: ...DONE
1395
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_with_time_limit.cc: ...
1396
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrp_with_time_limit.cc: ...DONE
1397
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrptw_store_solution_data.cc: ...
1398
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/constraint_solver/samples/vrptw_store_solution_data.cc: ...DONE
1399
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_groups_mip.cc: ...
1400
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_groups_mip.cc: ...DONE
1401
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_mip.cc: ...
1402
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_mip.cc: ...DONE
1403
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_task_sizes_mip.cc: ...
1404
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_task_sizes_mip.cc: ...DONE
1405
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_teams_mip.cc: ...
1406
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/assignment_teams_mip.cc: ...DONE
1407
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/basic_example.cc: ...
1408
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/basic_example.cc: ...DONE
1409
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/bin_packing_mip.cc: ...
1410
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/bin_packing_mip.cc: ...DONE
1411
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/integer_programming_example.cc: ...
1412
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/integer_programming_example.cc: ...DONE
1413
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/linear_programming_example.cc: ...
1414
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/linear_programming_example.cc: ...DONE
1415
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/mip_var_array.cc: ...
1416
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/mip_var_array.cc: ...DONE
1417
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/multiple_knapsack_mip.cc: ...
1418
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/multiple_knapsack_mip.cc: ...DONE
1419
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_lp_program.cc: ...
1420
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_lp_program.cc: ...DONE
1421
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_mip_program.cc: ...
1422
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/simple_mip_program.cc: ...DONE
1423
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/stigler_diet.cc: ...
1424
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/linear_solver/samples/stigler_diet.cc: ...DONE
1425
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/pdlp/samples/simple_pdlp_program.cc: ...
1426
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/pdlp/samples/simple_pdlp_program.cc: ...DONE
1427
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_groups_sat.cc: ...
1428
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_groups_sat.cc: ...DONE
1429
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_sat.cc: ...
1430
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_sat.cc: ...DONE
1431
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_task_sizes_sat.cc: ...
1432
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_task_sizes_sat.cc: ...DONE
1433
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_teams_sat.cc: ...
1434
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assignment_teams_sat.cc: ...DONE
1435
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assumptions_sample_sat.cc: ...
1436
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/assumptions_sample_sat.cc: ...DONE
1437
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/binpacking_problem_sat.cc: ...
1438
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/binpacking_problem_sat.cc: ...DONE
1439
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/bool_or_sample_sat.cc: ...
1440
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/bool_or_sample_sat.cc: ...DONE
1441
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/channeling_sample_sat.cc: ...
1442
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/channeling_sample_sat.cc: ...DONE
1443
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/copy_model_sample_sat.cc: ...
1444
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/copy_model_sample_sat.cc: ...DONE
1445
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_is_fun_sat.cc: ...
1446
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_is_fun_sat.cc: ...DONE
1447
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_sat_example.cc: ...
1448
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/cp_sat_example.cc: ...DONE
1449
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/earliness_tardiness_cost_sample_sat.cc: ...
1450
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/earliness_tardiness_cost_sample_sat.cc: ...DONE
1451
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/interval_sample_sat.cc: ...
1452
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/interval_sample_sat.cc: ...DONE
1453
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/literal_sample_sat.cc: ...
1454
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/literal_sample_sat.cc: ...DONE
1455
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/minimal_jobshop_sat.cc: ...
1456
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/minimal_jobshop_sat.cc: ...DONE
1457
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/multiple_knapsack_sat.cc: ...
1458
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/multiple_knapsack_sat.cc: ...DONE
1459
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/no_overlap_sample_sat.cc: ...
1460
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/no_overlap_sample_sat.cc: ...DONE
1461
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/non_linear_sat.cc: ...
1462
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/non_linear_sat.cc: ...DONE
1463
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nqueens_sat.cc: ...
1464
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nqueens_sat.cc: ...DONE
1465
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nurses_sat.cc: ...
1466
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/nurses_sat.cc: ...DONE
1467
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/optional_interval_sample_sat.cc: ...
1468
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/optional_interval_sample_sat.cc: ...DONE
1469
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/rabbits_and_pheasants_sat.cc: ...
1470
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/rabbits_and_pheasants_sat.cc: ...DONE
1471
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/ranking_sample_sat.cc: ...
1472
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/ranking_sample_sat.cc: ...DONE
1473
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/reified_sample_sat.cc: ...
1474
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/reified_sample_sat.cc: ...DONE
1475
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/schedule_requests_sat.cc: ...
1476
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/schedule_requests_sat.cc: ...DONE
1477
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/search_for_all_solutions_sample_sat.cc: ...
1478
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/search_for_all_solutions_sample_sat.cc: ...DONE
1479
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/simple_sat_program.cc: ...
1480
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/simple_sat_program.cc: ...DONE
1481
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solution_hinting_sample_sat.cc: ...
1482
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solution_hinting_sample_sat.cc: ...DONE
1483
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_and_print_intermediate_solutions_sample_sat.cc: ...
1484
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_and_print_intermediate_solutions_sample_sat.cc: ...DONE
1485
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_with_time_limit_sample_sat.cc: ...
1486
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/solve_with_time_limit_sample_sat.cc: ...DONE
1487
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/step_function_sample_sat.cc: ...
1488
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/step_function_sample_sat.cc: ...DONE
1489
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/stop_after_n_solutions_sample_sat.cc: ...
1490
- -- Configuring sample /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/ortools/sat/samples/stop_after_n_solutions_sample_sat.cc: ...DONE
1491
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/constraint_programming_cp.cc: ...
1492
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/constraint_programming_cp.cc: ...DONE
1493
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/costas_array_sat.cc: ...
1494
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/costas_array_sat.cc: ...DONE
1495
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cryptarithm_sat.cc: ...
1496
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cryptarithm_sat.cc: ...DONE
1497
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrp_disjoint_tw.cc: ...
1498
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrp_disjoint_tw.cc: ...DONE
1499
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw.cc: ...
1500
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw.cc: ...DONE
1501
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_resources.cc: ...
1502
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_resources.cc: ...DONE
1503
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_stop_times_and_resources.cc: ...
1504
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/cvrptw_with_stop_times_and_resources.cc: ...DONE
1505
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/flow_api.cc: ...
1506
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/flow_api.cc: ...DONE
1507
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/golomb_sat.cc: ...
1508
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/golomb_sat.cc: ...DONE
1509
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/integer_programming.cc: ...
1510
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/integer_programming.cc: ...DONE
1511
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_assignment_api.cc: ...
1512
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_assignment_api.cc: ...DONE
1513
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_programming.cc: ...
1514
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_programming.cc: ...DONE
1515
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_solver_protocol_buffers.cc: ...
1516
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/linear_solver_protocol_buffers.cc: ...DONE
1517
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_sequence_sat.cc: ...
1518
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_sequence_sat.cc: ...DONE
1519
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_square_sat.cc: ...
1520
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/magic_square_sat.cc: ...DONE
1521
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/max_flow.cc: ...
1522
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/max_flow.cc: ...DONE
1523
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/min_cost_flow.cc: ...
1524
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/min_cost_flow.cc: ...DONE
1525
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/nqueens.cc: ...
1526
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/nqueens.cc: ...DONE
1527
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/qap_sat.cc: ...
1528
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/qap_sat.cc: ...DONE
1529
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/random_tsp.cc: ...
1530
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/random_tsp.cc: ...DONE
1531
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/slitherlink_sat.cc: ...
1532
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/slitherlink_sat.cc: ...DONE
1533
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/uncapacitated_facility_location.cc: ...
1534
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/uncapacitated_facility_location.cc: ...DONE
1535
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/variable_intervals_sat.cc: ...
1536
- -- Configuring example /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/cpp/variable_intervals_sat.cc: ...DONE
1537
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/bug_fz1.cc: ...
1538
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/bug_fz1.cc: ...DONE
1539
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/cpp11_test.cc: ...
1540
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/cpp11_test.cc: ...DONE
1541
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/forbidden_intervals_test.cc: ...
1542
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/forbidden_intervals_test.cc: ...DONE
1543
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/init_test.cc: ...
1544
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/init_test.cc: ...DONE
1545
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue1303.cc: ...
1546
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue1303.cc: ...DONE
1547
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue173.cc: ...
1548
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue173.cc: ...DONE
1549
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue57.cc: ...
1550
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/issue57.cc: ...DONE
1551
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/lp_test.cc: ...
1552
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/lp_test.cc: ...DONE
1553
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/min_max_test.cc: ...
1554
- -- Configuring test /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/examples/tests/min_max_test.cc: ...DONE
1555
- -- Configuring done
1556
- -- Generating done
1557
- -- Build files have been written to: /home/ikenna/Work/vlsi/tools/OpenROAD-flow-scripts/or-tools/build
1558
- gmake: Makefile: No such file or directory
1559
- gmake: *** No rule to make target 'Makefile'. Stop.
1560
-
1561
- ```
1562
-
1563
- ### vvbandeira
1564
- @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?
1565
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/4269.md DELETED
@@ -1,52 +0,0 @@
1
- # How to add new classes/structures to OpenROAD's schema?
2
-
3
- Tool: OpenDB
4
-
5
- Subcategory: Code generation issue
6
-
7
- ## Conversation
8
-
9
- ### fgaray
10
- Hello OpenRoad devs,
11
-
12
- 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.
13
-
14
- See: https://github.com/fgaray/OpenROAD/tree/ctl_db, path src/odb/src/codeGenerator/schema/scan
15
-
16
- I am adding 3 new *.json files: dbScanInst.json dbScanPartition.json dbScanPin.json
17
-
18
- In dbScanPin.json I am defining an "union" of dbBTerm and dbITerm
19
-
20
- In dbScanPartition.json I am trying to use dbScanPin for my "start" and "stop" fields.
21
-
22
-
23
- I am running the ./generate script in src/odb/src/codeGenerator to generate the C++ code but I am getting the following error:
24
-
25
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/1619948/fc8774d8-b742-4407-86ef-e877d347f5d3)
26
-
27
- 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.
28
-
29
- Is there an step that I am missing or maybe some config?
30
-
31
- Thanks!
32
-
33
-
34
- ### maliberty
35
- Use dbId to store references to other db objects
36
- ```
37
- "name": "start",
38
- - "type": "dbScanPin"
39
- + "type": "dbId<dbScanPin>"
40
- },
41
- {
42
- "name": "stop",
43
- - "type": "dbScanPin"
44
- + "type": "dbId<dbScanPin>"
45
- },
46
- ```
47
-
48
- ### fgaray
49
- I forgot to close this issue, but the answer was given by @maliberty .
50
-
51
- Writing the custom setter was the way to go when implementing this.
52
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/4956.md DELETED
@@ -1,67 +0,0 @@
1
- # OpenROAD Build From Sources
2
-
3
- Subcategory: Compilation error
4
-
5
- ## Conversation
6
-
7
- ### sebinho
8
- Hello Guys,
9
-
10
- I am using ArchLinux and I have been using OpenROAD from an install package from the AUR.
11
- This install does not seem to work anymore (it was working on my setup a couple of weeks ago).
12
-
13
- So I am trying to build from sources but I get the same errors as I get with the AUR package:
14
- ```
15
- [ 74%] Building CXX object src/gui/CMakeFiles/gui.dir/src/scriptWidget.cpp.o
16
- In file included from /home/zed/repos/OpenROAD/src/gui/src/tclCmdInputWidget.h:50,
17
- from /home/zed/repos/OpenROAD/src/gui/src/scriptWidget.cpp:49:
18
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h: In function ‘int SWIG_Tcl_GetArgs(Tcl_Interp*, int, Tcl_Obj* const*, const char*, ...)’:
19
- /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’?
20
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
21
- | ^~~~~~~~
22
- | Tcl_Time
23
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:21: error: ‘vlptr’ was not declared in this scope; did you mean ‘vptr’?
24
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
25
- | ^~~~~
26
- | vptr
27
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:40: error: expected primary-expression before ‘)’ token
28
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
29
- | ^
30
- make[2]: *** [src/gui/CMakeFiles/gui.dir/build.make:226: src/gui/CMakeFiles/gui.dir/src/scriptWidget.cpp.o] Error 1
31
- make[2]: *** Waiting for unfinished jobs....
32
- [ 74%] Building CXX object src/rcx/src/CMakeFiles/rcxUnitTest.dir/__/test/ext2dBoxTest.cpp.o
33
- In file included from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/UVLADIE3JM/../../../../../src/gui/src/tclCmdInputWidget.h:50,
34
- from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/UVLADIE3JM/moc_tclCmdInputWidget.cpp:10,
35
- from /home/zed/repos/OpenROAD/build/src/gui/gui_autogen/mocs_compilation.cpp:23:
36
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h: In function ‘int SWIG_Tcl_GetArgs(Tcl_Interp*, int, Tcl_Obj* const*, const char*, ...)’:
37
- /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’?
38
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
39
- | ^~~~~~~~
40
- | Tcl_Time
41
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:21: error: ‘vlptr’ was not declared in this scope; did you mean ‘vptr’?
42
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
43
- | ^~~~~
44
- | vptr
45
- /home/zed/repos/OpenROAD/build/src/gui/tclSwig.h:1623:40: error: expected primary-expression before ‘)’ token
46
- 1623 | Tcl_Size *vlptr = (Tcl_Size *) va_arg(ap, void *);
47
- | ^
48
- [ 74%] Linking CXX executable dpl_test
49
- ```
50
-
51
- Seems to be something related to Swig with TCL. Does anybody know what the problem is?
52
-
53
- Thanks for your help
54
-
55
-
56
-
57
- ### maliberty
58
- What version of TCL and swig do you have installed?
59
-
60
- ### maliberty
61
- 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?
62
-
63
- ### stefanottili
64
- Does anybody know how to downgrade swig on MacOS M1 homebrew ?
65
- The current SWIG Version 4.2.1 causes the same error here.
66
- Can be worked around by commenting out the two offending lines, they seem to be in an error path ...
67
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Build/5101.md DELETED
@@ -1,31 +0,0 @@
1
- # OpenROAD build with recent versions of FMT and SPDLOG
2
-
3
- Subcategory: Dependency compatibility issues
4
-
5
- ## Conversation
6
-
7
- ### sebinho
8
- 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.
9
- The issues I had seem to be related to more recent versions of spdlog and fmt packages.
10
- 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).
11
-
12
- The issues were as follows during the build (one example, others are similar):
13
-
14
- ```
15
- /usr/include/fmt/core.h:1600:63: error: ‘fmt::v10::detail::type_is_unformattable_for<const dpl::TypedCoordinate<dpl::GridYType>, char> _’ has incomplete type
16
- 1600 | type_is_unformattable_for<T, typename Context::char_type> _;
17
- | ^
18
- /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
19
- 1604 | formattable,
20
- | ^~~~~~~~~~~
21
- /usr/include/fmt/core.h:1604:7: note: ‘formattable’ evaluates to false
22
- ```
23
-
24
- 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`
25
-
26
- ### rovinski
27
- 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.
28
-
29
- ### maliberty
30
- Please see my comment about FMT_DEPRECATED_OSTREAM in https://github.com/The-OpenROAD-Project/OpenROAD/pull/2696
31
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/2442.md DELETED
@@ -1,20 +0,0 @@
1
- # Unable to find image 'openroad/flow-scripts:latest' locally
2
-
3
- Subcategory: Docker setup issue
4
-
5
- ## Conversation
6
-
7
- ### heaton56
8
- After install, trying to run the docker I get the following. ny ideas?
9
-
10
- Unable to find image 'openroad/flow-scripts:latest' locally
11
- 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.
12
-
13
- ### maliberty
14
- How did you 'install' it? What command did you run that gave this message?
15
-
16
- ### heaton56
17
- 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.
18
-
19
-
20
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/3350.md DELETED
@@ -1,41 +0,0 @@
1
- # Which distros to support
2
-
3
- Subcategory: Environment setup
4
-
5
- ## Conversation
6
-
7
- ### maliberty
8
- Currently OR CI is built with
9
- * Local centos7 gcc8
10
- * Local centos7 gcc8 without GUI
11
- * Docker centos7 gcc8
12
- * Docker ubuntu20.04 gcc9
13
-
14
- PRs additionally have GH actions that test:
15
- * macOS (x86)
16
- * c++20 (using clang-16)
17
-
18
- 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.
19
-
20
- 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
21
-
22
- The default compiler version would be updated to match the distro default.
23
-
24
- FYI @vvbandeira @tspyrou
25
-
26
- ### QuantamHD
27
- Google is on Debian test called [Glinux](https://en.wikipedia.org/wiki/GLinux). Ubuntu 22 or Debian 11 seem like reasonable choices to me.
28
-
29
- 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.
30
-
31
- Google has a one version policy for any piece of software in the universe, and it's all stored in a monorepo.
32
-
33
- ### donn
34
- 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.
35
-
36
- ### rovinski
37
- 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.
38
-
39
- ### olofk
40
- 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
41
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/3943.md DELETED
@@ -1,35 +0,0 @@
1
- # How to develop the " setRC.tcl " file from a captable for a foreign PDK ?
2
-
3
- Tool: Parasitics Extraction
4
-
5
- Subcategory: Setting up foreign PDK
6
-
7
- ## Conversation
8
-
9
- ### faisaladilquadery
10
- 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 .
11
-
12
- N.B : I have a captable for the pdk
13
- I can also generate a spef file from Innovus for the PDK
14
-
15
- ### maliberty
16
- @vvbandeira @luarss do we have any documentation for correlateRC ?
17
-
18
- Note that if you LEF res & cap has values you can use those without a setRC to get started.
19
-
20
- ### vvbandeira
21
- @faisaladilquadery
22
- We have a section on the `setRC.tcl` file configuration in our platform bring-up documentation.
23
- https://openroad-flow-scripts.readthedocs.io/en/latest/contrib/PlatformBringUp.html#setrc-configuration
24
-
25
- ### faisaladilquadery
26
- 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 ?
27
-
28
- ### faisaladilquadery
29
- 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.
30
-
31
- ### b224hisl
32
- > 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.
33
-
34
- 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?
35
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/4289.md DELETED
@@ -1,31 +0,0 @@
1
- # Disable LEF Warning Messages
2
-
3
- Tool: OpenDB
4
-
5
- Subcategory: Warnings and messages
6
-
7
- ## Conversation
8
-
9
- ### abaababa
10
- Hi all,
11
-
12
- 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.
13
-
14
- Thanks in advance!
15
-
16
-
17
-
18
- ### maliberty
19
- There is no method to do that currently. No single message will print more than 1k times.
20
-
21
- ### luarss
22
- @maliberty Correct me if I am wrong, but doesn't Tcl function `suppress_message` do this?
23
-
24
- Edit: i guess there's no function that achieves full suppression for all warnings, what OP requested
25
-
26
- https://github.com/The-OpenROAD-Project/OpenROAD/blob/28892de3bef1af52f3371d547f752acf0af20021/test/helpers.tcl#L203
27
-
28
- Corresponding source:
29
- https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/utl/src/Logger.cpp
30
-
31
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/4515.md DELETED
@@ -1,23 +0,0 @@
1
- # How do I avoid cells rotation in placement?
2
-
3
- Tool: Detailed Placement
4
-
5
- Subcategory: Cell placement rules
6
-
7
- ## Conversation
8
-
9
- ### OuDret
10
- 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.
11
-
12
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/74424277/9d1b472c-dac6-4458-a3f6-f045e42abcfc)
13
-
14
- Thanks
15
-
16
-
17
-
18
- ### maliberty
19
- If it is a standard cell the LEF for the cell gives its symmetry.
20
-
21
- ### maliberty
22
- 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.
23
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/5065.md DELETED
@@ -1,155 +0,0 @@
1
- # howo to run openroad by reading an existing DEF file
2
-
3
- Tool: OpenDB
4
-
5
- Subcategory: Initialization from existing DEF
6
-
7
- ## Conversation
8
-
9
- ### bittnada
10
- Hello
11
- I have a DEF file in which row, track, components, and pins are written.
12
- The position of the cells are on the step of global placement, obtained by using another method.
13
- Now, I want to finish the rest of the procedures by modifying "test/flow.tcl" file.
14
- I just skipped the steps of pin placement and global placement and added "read_def [my_def_fiel}'", but it did not work.
15
- I will appreciate if anyone let me know how to solve this problem.
16
- Thanks,
17
-
18
-
19
-
20
- ### maliberty
21
- What happened when it "did not work"? Its not much to go on.
22
-
23
- ### bittnada
24
-
25
- Sorry for my delayed response.
26
-
27
- 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".
28
-
29
- After running gcd_nangate45.tcl, I received the following output:
30
-
31
- ====================================================================================
32
- OpenROAD v2.0-13652-g6fc686431
33
- Features included (+) or not (-): +Charts +GPU +GUI +Python
34
- This program is licensed under the BSD-3 license. See the LICENSE file for details.
35
- Components of this program may be licensed under more restrictive licenses which must be honored.
36
- [INFO ODB-0227] LEF file: Nangate45/Nangate45_tech.lef, created 22 layers, 27 vias
37
- [INFO ODB-0227] LEF file: Nangate45/Nangate45_stdcell.lef, created 135 library cells
38
- [WARNING STA-0441] set_input_delay relative to a clock defined on the same port/pin not allowed.
39
- [INFO IFP-0001] Added 57 rows of 422 site FreePDK45_38x28_10R_NP_162NW_34O.
40
- [INFO ORD-0048] Loading an additional DEF.
41
- Error: Chip already exists
42
- [INFO RSZ-0058] Using max wire length 693um.
43
- [INFO RSZ-0039] Resized 41 instances.
44
- Placement Analysis
45
- ---------------------------------
46
- total displacement 17739.5 u
47
- average displacement 49.0 u
48
- max displacement 62.9 u
49
- original HPWL 280.4 u
50
- legalized HPWL 9839.7 u
51
- delta HPWL 3410 %
52
-
53
- worst slack 0.105
54
- worst slack -0.011
55
- tns -0.011
56
- [INFO CTS-0050] Root buffer is BUF_X4.
57
- [INFO CTS-0051] Sink buffer is BUF_X4.
58
- [INFO CTS-0052] The following clock buffers will be used for CTS:
59
- BUF_X4
60
- [INFO CTS-0049] Characterization buffer is BUF_X4.
61
- [INFO CTS-0007] Net "clk" found for clock "core_clock".
62
- [WARNING CTS-0041] Net "clk" has 0 sinks. Skipping...
63
- [WARNING CTS-0083] No clock nets have been found.
64
- [INFO CTS-0008] TritonCTS found 0 clock nets.
65
- [WARNING CTS-0082] No valid clock nets in the design.
66
- [INFO RSZ-0058] Using max wire length 693um.
67
- Placement Analysis
68
- ---------------------------------
69
- total displacement 0.0 u
70
- average displacement 0.0 u
71
- max displacement 0.0 u
72
- original HPWL 9839.7 u
73
- legalized HPWL 9839.7 u
74
- delta HPWL 0 %
75
-
76
- [INFO RSZ-0094] Found 1 endpoints with setup violations.
77
- [WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
78
- [WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
79
- [WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
80
- [WARNING RSZ-0075] makeBufferedNet failed for driver _393_/ZN
81
- [INFO RSZ-0041] Resized 5 instances.
82
- [INFO RSZ-0043] Swapped pins on 2 instances.
83
- [INFO RSZ-0033] No hold violations found.
84
- worst slack 0.106
85
- worst slack 0.000
86
- tns 0.000
87
- Placement Analysis
88
- ---------------------------------
89
- total displacement 91.3 u
90
- average displacement 0.3 u
91
- max displacement 6.4 u
92
- original HPWL 9840.8 u
93
- legalized HPWL 9925.0 u
94
- delta HPWL 1 %
95
-
96
- [INFO DRT-0149] Reading tech and libs.
97
-
98
- Units: 2000
99
- Number of layers: 21
100
- Number of macros: 135
101
- Number of vias: 27
102
- Number of viarulegen: 19
103
-
104
- Signal 11 received
105
- Stack trace:
106
- 0# 0x0000564758181A44 in /mnt/work/OpenROAD/bin/bin/openroad
107
- 1# 0x00007F4028F54F10 in /lib/x86_64-linux-gnu/libc.so.6
108
- 2# odb::dbTechVia::getTopLayer() in /mnt/work/OpenROAD/bin/bin/openroad
109
- 3# odb::dbWireEncoder::addTechVia(odb::dbTechVia*) in /mnt/work/OpenROAD/bin/bin/openroad
110
- 4# drt::TritonRoute::stackVias(odb::dbBTerm*, int, int, bool) in /mnt/work/OpenROAD/bin/bin/openroad
111
- 5# drt::TritonRoute::processBTermsAboveTopLayer(bool) in /mnt/work/OpenROAD/bin/bin/openroad
112
- 6# drt::TritonRoute::initDesign() in /mnt/work/OpenROAD/bin/bin/openroad
113
- 7# drt::TritonRoute::pinAccess(std::vector<odb::dbInst*, std::allocator<odb::dbInst*> > const&) in /mnt/work/OpenROAD/bin/bin/openroad
114
- 8# pin_access_cmd(char const*, char const*, char const*, int, int) in /mnt/work/OpenROAD/bin/bin/openroad
115
- 9# 0x00005647589E491B in /mnt/work/OpenROAD/bin/bin/openroad
116
- 10# TclNRRunCallbacks in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
117
- 11# 0x00007F402E79BFBA in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
118
- 12# Tcl_EvalEx in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
119
- 13# Tcl_Eval in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
120
- 14# gui::TclCmdInputWidget::executeCommand(QString const&, bool, bool) in /mnt/work/OpenROAD/bin/bin/openroad
121
- 15# gui::CmdInputWidget::handleEnterKeyPress(QKeyEvent*) in /mnt/work/OpenROAD/bin/bin/openroad
122
- 16# gui::TclCmdInputWidget::keyPressEvent(QKeyEvent*) in /mnt/work/OpenROAD/bin/bin/openroad
123
- 17# QWidget::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
124
- 18# QFrame::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
125
- 19# QAbstractScrollArea::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
126
- 20# QPlainTextEdit::event(QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
127
- 21# QApplicationPrivate::notify_helper(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
128
- 22# QApplication::notify(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
129
- 23# QCoreApplication::notifyInternal2(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
130
- 24# 0x00007F402B1357B5 in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
131
- 25# QApplicationPrivate::notify_helper(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
132
- 26# QApplication::notify(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
133
- 27# QCoreApplication::notifyInternal2(QObject*, QEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
134
- 28# QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
135
- 29# QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
136
- 30# QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
137
- 31# 0x00007F4022595260 in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
138
- 32# g_main_context_dispatch in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
139
- 33# 0x00007F402783C770 in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
140
- 34# g_main_context_iteration in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
141
- 35# QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
142
- 36# QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
143
- 37# QCoreApplication::exec() in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
144
- 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
145
- 39# ord::tclAppInit(Tcl_Interp*) in /mnt/work/OpenROAD/bin/bin/openroad
146
- 40# Tcl_MainEx in /usr/lib/x86_64-linux-gnu/libtcl8.6.so
147
- 41# main in /mnt/work/OpenROAD/bin/bin/openroad
148
- 42# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
149
- 43# _start in /mnt/work/OpenROAD/bin/bin/openroad
150
- ================================================================================================
151
-
152
- 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.
153
-
154
- Thanks.
155
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/5199.md DELETED
@@ -1,24 +0,0 @@
1
- # Non-rectilinear core area
2
-
3
- Tool: Initialize Floorplan
4
-
5
- Subcategory: Floorplan customization
6
-
7
- ## Conversation
8
-
9
- ### Blebowski
10
- Hello,
11
-
12
- is it possible to somehow specify core-area that is non-rectilinear (e.g. as a group of polygons surrounding concave shape) ?
13
-
14
- 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.
15
-
16
-
17
-
18
- ### maliberty
19
- The simplest would be to make a rectangular block and add placement and routing blockages for the disallowed area
20
-
21
- ### Blebowski
22
- 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
23
- to achieve this ?
24
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Configuration/5213.md DELETED
@@ -1,66 +0,0 @@
1
- # Running a simple combinatorial design
2
-
3
- Tool: OpenDB
4
-
5
- Subcategory: Module name mismatch
6
-
7
- ## Conversation
8
-
9
- ### Dandy201
10
- Hi all, I'm new to using ORFS and tried some tutorials from https://github.com/The-OpenROAD-Project/micro2022tutorial.
11
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/8a6e4ccd-503a-4751-8ead-8c1c5d209890)
12
-
13
- Completing exercise 5 got this simple output:
14
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/63ead36e-c51b-456b-9526-819d76f8a209).
15
-
16
- 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:
17
-
18
- 7. Executing Verilog-2005 frontend: /home/dan/Desktop/Work/vlsi/tools/OpenROAD-flow-scripts/flow/platforms/asap7/yoSys/cells_clkgate_R.v
19
- Using ABC speed script.
20
- [FLOW] Extracting clock period from SDC file: ./results/asap7/halfAdder/base/clock_period.txt
21
- [FLOW] Setting clock period to 5
22
- 8. Executing SYNTH pass.
23
- 8.1. Executing HIERARCHY pass (managing design hierarchy).
24
- **ERROR: TCL interpreter returned an error: Yosys command produced an error
25
- Command exited with non-zero status 1
26
- Elapsed time: 0:00.59[h:]min:sec. CPU time: user 0.56 sys 0.02 (99%). Peak memory: 72508KB.
27
- make[1]: *** [Makefile:496: do-yosys] Error 1
28
- make: *** [Makefile:499: results/asap7/halfAdder/base/1_1_yosys.v] Error 2.**
29
-
30
- Config file
31
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/324abeb8-c78c-42a6-906f-811f9c4134b6)
32
-
33
- Constraint file
34
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/c305c964-35a7-4fae-b038-7cbb9539f98d)
35
-
36
- Verilog file
37
- ![image](https://github.com/The-OpenROAD-Project/OpenROAD/assets/172090682/fe9cc773-67be-4235-a4b5-b66b06dee795)
38
-
39
-
40
-
41
-
42
-
43
- ### maliberty
44
- Please package this as a standalone test case and attach it. Reproducing it from screen shots is inefficient.
45
-
46
- ### Dandy201
47
- [try.zip](https://github.com/user-attachments/files/15751707/try.zip)
48
-
49
- Here's the zip file along with the command : make DESIGN_CONFIG=../../try/config.mk
50
-
51
-
52
- ### mi-and-core
53
- (1) change module name from 'half_adder' to 'halfAdder'
54
-
55
-
56
- ### maliberty
57
- In the config.mk
58
- ```
59
- export DESIGN_NAME = halfAdder
60
- ```
61
- while in halfAdder.v:
62
- ```
63
- module half_adder(
64
- ```
65
- These names need to match.
66
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Documentation/4495.md DELETED
@@ -1,27 +0,0 @@
1
- # pad_left/right units for GPL and repair_clock_inverters description
2
-
3
- Tool: Global Placement
4
-
5
- Subcategory: Missing information
6
-
7
- ## Conversation
8
-
9
- ### lustefan97
10
-
11
-
12
- 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)
13
-
14
- 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`.
15
-
16
- What are the units of pad_left/right, and what does `repair_clock_inverters` do/how to use it ?
17
-
18
- ### maliberty
19
- The units are sites from the LEF.
20
-
21
- 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.
22
-
23
- ### maliberty
24
- before CTS see https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/181e9133776117ea1b9f74dbacbfdaadff8c331b/flow/scripts/cts.tcl#L7
25
-
26
- You might benefit from investigating how ORFS works
27
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Documentation/5312.md DELETED
@@ -1,34 +0,0 @@
1
- # How to query odb database
2
-
3
- Tool: OpenDB
4
-
5
- Subcategory: Incomplete documentation
6
-
7
- ## Conversation
8
-
9
- ### titan73
10
- I want to directly query odb database. How can I do that? There is no command for that.
11
- I found some ord::xxx commands by searching the net but there is no proper documentation with all commands.
12
-
13
- ### titan73
14
- also found odb::xxx. No documentation either.
15
- Most functions required a self argument.
16
- Tested "::odb::dbBlock_getPowerDomains [::odb::dbBlock]" to get power domains but it crashes.
17
-
18
- ### titan73
19
- I got to something using orf and odb to get the created power domains:
20
-
21
- foreach pd [::odb::dbBlock_getPowerDomains [::ord::get_db_block]] {
22
- puts "[::odb::dbPowerDomain_getName $pd]"
23
- }
24
-
25
- I think I get the idea. A pity it's not documented.
26
-
27
-
28
- ### maliberty
29
- 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.
30
-
31
- ### titan73
32
- Ok thanks. It helps. Although not all methods have comments. dbPowerDomain for instance.
33
- How does int& is supposed to be mapped in tcl? Ex: bool getArea(int& x1, int& y1, int& x2, int& y2);
34
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/2679.md DELETED
@@ -1,37 +0,0 @@
1
- # How can I run the OpenROAD GUI on Ubuntu locally and not in Docker?
2
-
3
- Tool: Graphical User Interface
4
-
5
- Subcategory: Local installation
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- How can I install and run the OpenROAD GUI locally?
11
-
12
- 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.
13
-
14
- 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?
15
-
16
- 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.
17
-
18
- https://github.com/The-OpenROAD-Project/OpenROAD/issues/2675#issue-1513733033
19
-
20
-
21
- 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
22
-
23
-
24
-
25
- ### QuantamHD
26
- Creating a snap package in the CI might be a good option https://ubuntu.com/tutorials/create-your-first-snap#1-overview
27
-
28
- ### maliberty
29
- 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).
30
-
31
- I'm surprised using docker makes much of a difference for the GUI. What do you see?
32
-
33
- You can always mount your directory in docker so envars shouldn't be a big issue.
34
-
35
- ### mithro
36
- Have you tried the conda packages?
37
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/2971.md DELETED
@@ -1,43 +0,0 @@
1
- # Arm64 Support
2
-
3
- Subcategory: Architecture compatibility
4
-
5
- ## Conversation
6
-
7
- ### DylanTom
8
- Hi, I am looking to use OpenROAD and have tried to install it on my computer.
9
-
10
- 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.
11
-
12
- 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.
13
-
14
- Specifically, does OpenROAD support the ARM architecture, and if not, is that a priority in the future?
15
-
16
- Thanks!
17
-
18
- ### vijayank88
19
- Can you try OpenROAD-flow-scripts with docker based: https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildWithDocker.html#clone-and-build
20
-
21
- ### maliberty
22
- 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.
23
-
24
- ### vvbandeira
25
- > Note: OR-Tools only provides archives for the x86_64 (also known as amd64) architecture.
26
- Source: https://developers.google.com/optimization/install/cpp/binary_linux
27
-
28
- @DylanTom If you are already using a VM, you can create a x86_64 VM and avoid this issue.
29
-
30
- ### stefanottili
31
- If you're on M2, why not give "native" OR a try ?
32
-
33
- I've been compiling it on and off using HomeBrew for dependencies (including or-tools) for a while now.
34
- or-tools and mpl2 keep on breaking the build and mpl2 is still be disabled.
35
- >> -- Removing MPL2 and PAR to avoid run time fatal error.
36
-
37
- So occasionally it doesn't work, but most of the times I got it to compile in < 15min on a M1.
38
-
39
- etc/DependencyInstaller.sh (unforunately now installs x86 klayout, I prefer building it natively)
40
- ./build_openroad.sh --local --latest --clean-force (breaks today in a mpl2 test)
41
- ./build_openroad.sh --local (when run again it finishes, go figure)
42
-
43
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/2972.md DELETED
@@ -1,102 +0,0 @@
1
- # CMAKE errors while installing Openroad
2
-
3
- Subcategory: Build issues
4
-
5
- ## Conversation
6
-
7
- ### mdzaki-git
8
- HI All,
9
-
10
- After installing the dependencies we re stuck with cmake errors and would appreciate your help in fixing them. Attaching the error snippet for reference.
11
- <img width="1388" alt="Cmake Error" src="https://user-images.githubusercontent.com/68725332/223042193-39b47832-730e-4716-abce-421e7a44dfc8.png">
12
-
13
-
14
- ### vijayank88
15
- attach log `build_openroad.log`
16
-
17
- ### mdzaki-git
18
- [openroad_build.log](https://github.com/The-OpenROAD-Project/OpenROAD/files/10897535/openroad_build.log)
19
-
20
-
21
- ### mdzaki-git
22
- Following the install instruction mentioned on git hub.
23
- https://github.com/The-OpenROAD-Project/OpenROAD
24
-
25
- ### mdzaki-git
26
- Hi Vitor,
27
-
28
- Recloned the repository and tried again, getting below errors now.
29
-
30
-
31
-
32
- On Mon, Mar 6, 2023 at 7:32 PM Vitor Bandeira ***@***.***>
33
- wrote:
34
-
35
- > @vijayank88 <https://github.com/vijayank88>, this warning is not a
36
- > problem with CMake; this indicates that the folder is not a git repo.
37
- > @mdzaki-git <https://github.com/mdzaki-git>, can you make sure that the
38
- > clone ended fine? Maybe check the output of git status --long, the output
39
- > of this command should look something like this:
40
- >
41
- > > git status --long
42
- > On branch master
43
- > Your branch is up to date with 'origin/master'.
44
- > nothing to commit, working tree clean
45
- >
46
- > Also, try to do a clean build and in case of any errors upload the new log
47
- > file.
48
- >
49
- > ./etc/Build.sh -clean
50
- >
51
- > —
52
- > Reply to this email directly, view it on GitHub
53
- > <https://github.com/The-OpenROAD-Project/OpenROAD/discussions/2972#discussioncomment-5216244>,
54
- > or unsubscribe
55
- > <https://github.com/notifications/unsubscribe-auth/AQMKUVEUTV4F7PDCH6F4IQ3W2XU6HANCNFSM6AAAAAAVQXMFI4>
56
- > .
57
- > You are receiving this because you were mentioned.Message ID:
58
- > <The-OpenROAD-Project/OpenROAD/repo-discussions/2972/comments/5216244@
59
- > github.com>
60
- >
61
-
62
-
63
- ### mdzaki-git
64
- [openroad_build.log](https://github.com/The-OpenROAD-Project/OpenROAD/files/10899446/openroad_build.log)
65
-
66
-
67
- ### vvbandeira
68
- Looks like you missed the `--recursive` when cloning. Please run
69
-
70
- ```
71
- git submodule update --init
72
- ```
73
-
74
- In the future you should use `git clone --recursive` to also clone the submodules `abc` and `sta`.
75
-
76
- ### mdzaki-git
77
- Hi All,
78
-
79
- Thanks it works now.
80
-
81
- On Mon, Mar 6, 2023 at 9:37 PM Vitor Bandeira ***@***.***>
82
- wrote:
83
-
84
- > Looks like you missed the --recursive when cloning. Please run
85
- >
86
- > git submodule update --init
87
- >
88
- > In the future you should use git clone --recursive to also clone the
89
- > submodules abc and sta.
90
- >
91
- > —
92
- > Reply to this email directly, view it on GitHub
93
- > <https://github.com/The-OpenROAD-Project/OpenROAD/discussions/2972#discussioncomment-5217710>,
94
- > or unsubscribe
95
- > <https://github.com/notifications/unsubscribe-auth/AQMKUVH4OMC266IZBNAHYATW2YDTFANCNFSM6AAAAAAVQXMFI4>
96
- > .
97
- > You are receiving this because you were mentioned.Message ID:
98
- > <The-OpenROAD-Project/OpenROAD/repo-discussions/2972/comments/5217710@
99
- > github.com>
100
- >
101
-
102
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/3004.md DELETED
@@ -1,107 +0,0 @@
1
- # openRoad installation
2
-
3
- Subcategory: Dependency issues
4
-
5
- ## Conversation
6
-
7
- ### msingh9
8
- I was successfully able to run cmake and then make. However, output of cmake has following two messages which seems problematic to me. How do I resolve these?
9
-
10
- -- GUI is not enabled
11
- -- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS)
12
-
13
- I ran following command
14
- cmake .. -DCMAKE_INSTALL_PREFIX=/home/msingh/openRoad -DPYTHON_INCLUDE_DIR=$(python3 -c "import sysconfig; print(sysconfig.get_path('include'))") -DPYTHON_LIBRARY=$(python3 -c\
15
- "import sysconfig; print(sysconfig.get_config_var('LIBDIR'))")
16
-
17
- I also ran make afterwards, which seems to finish. There are bunch of warnings but no error message. Where do I find the executable. I don't find it in CMAKE_INSTALL_PREFIX/bin directory.
18
-
19
- Does it mean that installation didn't complete?
20
-
21
- I am looking for some help because I am stuck in the installation.
22
-
23
- I just cleared the buffer that has log, but I can redo those steps if you need the complete log output.
24
-
25
- ### maliberty
26
- Vtune is unimportant unless you are a developer of OR.
27
-
28
- The GUI suggests that you don't have Qt installed. Did you run the dependency installer?
29
-
30
- ### msingh9
31
- Thanks Maliberty for response.
32
-
33
- I followed the steps "https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildLocally.html" and was able to build with hiccups.
34
- How do I make sure Qt is installed? BTW - I am trying to install it on Linux RH8. Is it supported platform?
35
-
36
- When I try to invoke it, I get this missing library error.
37
- openroad -help
38
- openroad: error while loading shared libraries: libortools.so.9: cannot open shared object file: No such file or directory
39
-
40
-
41
- ### maliberty
42
- I don't know what OS you are on and you haven't included any logs. If you look at https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/etc/DependencyInstaller.sh it you'll see it references Qt libraries.
43
-
44
- ### msingh9
45
- I am trying to build it on RH8. I am really stuck at this point now. I ran "sudo ./DependencyInstaller.sh" successfully.
46
-
47
- I can check that qt5 is installed.
48
-
49
- [msingh@lnx-msingh cv6 /tmp]$ sudo yum -y install qt5-srpm-macros.noarch
50
- Last metadata expiration check: 0:07:51 ago on Sun 12 Mar 2023 12:19:34 AM PST.
51
- Package qt5-srpm-macros-5.12.5-3.el8.noarch is already installed.
52
- Dependencies resolved.
53
- Nothing to do.
54
-
55
- When I run cmake to create build files, I get that "GUI is not enabled". Is there a switch I need to pass to cmake. Here is my command and it's output.
56
-
57
- [msingh@lnx-msingh cv6 build]$ cmake .. -DPYTHON_INCLUDE_DIR=/cv6/tools2/tv2/release/Python3/3.9.0/include/python3.9 -DPYTHON_LIBRARY=/cv6/tools2/tv2/release/Python3/3.9.0/lib -Dortools_DIR=/opt/or-tools
58
- -- OpenROAD version: v2.0-7131-g1d8d24209
59
- -- System name: Linux
60
- -- Compiler: GNU 8.3.1
61
- -- Build type: RELEASE
62
- -- Install prefix: /usr/local
63
- -- C++ Standard: 17
64
- -- C++ Standard Required: ON
65
- -- C++ Extensions: OFF
66
- -- TCL library: /usr/lib64/libtcl.so
67
- -- TCL header: /usr/include/tcl.h
68
- -- TCL readline library: /usr/lib64/libtclreadline.so
69
- -- TCL readline header: /usr/include
70
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0")
71
- -- boost: 1.80.0
72
- -- spdlog: 1.8.1
73
- -- STA version: 2.4.0
74
- -- STA git sha: f84e617fc435d2d280a3f76045aa461afa386e2b
75
- -- System name: Linux
76
- -- Compiler: GNU 8.3.1
77
- -- Build type: RELEASE
78
- -- Build CXX_FLAGS: -O3 -DNDEBUG
79
- -- Install prefix: /usr/local
80
- -- TCL library: /usr/lib64/libtcl.so
81
- -- TCL header: /usr/include/tcl.h
82
- -- SSTA: 0
83
- -- STA executable: /dump/vlsidump302/msingh/OpenROAD/src/sta/app/sta
84
- -- GPU is not enabled
85
- -- GUI is not enabled
86
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization
87
- -- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS)
88
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found suitable version "1.80.0", minimum required is "1.78")
89
- -- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization system thread
90
- -- TCL readline enabled
91
- -- Tcl Extended disabled
92
- -- Python3 disabled
93
- -- Configuring done
94
- -- Generating done
95
- -- Build files have been written to: /dump/vlsidump302/msingh/OpenROAD/build
96
-
97
-
98
- ### maliberty
99
- What OS are you using? Is qt in the default location?
100
-
101
- ### vijayank88
102
- @msingh9
103
- Can you try docker based installation [steps](https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildWithDocker.html) ?
104
-
105
- ### msingh9
106
- Thank you everyone for support. I finally managed to make it work on RH8. It is exciting to see this tool in action. I really like to appreciate everyone effort to make this open-source magic. I will post my results once I can make it work.
107
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/4162.md DELETED
@@ -1,23 +0,0 @@
1
- # Libfmt v8 required for conda installation
2
-
3
- Subcategory: Dependency issue
4
-
5
- ## Conversation
6
-
7
- ### chetanyagoyal
8
- Trying to use
9
- openroad==2.0_10145_g0de6f5131 installed with conda gives the following error -
10
- `openroad: error while loading shared libraries: libfmt.so.8: cannot open shared object file: No such file or directory`
11
-
12
- This error occurs only on Ubuntu20.04 because libfmt version 8 does not exist for it.
13
- Are there any workarounds to this?
14
-
15
- ### rovinski
16
- I don't think we host a conda installation. The installer would be from a third party and you should ask them for support.
17
-
18
- ### maliberty
19
- @proppy is the conda installer something you support?
20
-
21
- ### proppy
22
- yes, it seems they already filed an issue over at https://github.com/hdl/conda-eda/issues/360 (so feel free to close the issue here).
23
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Installation/4653.md DELETED
@@ -1,20 +0,0 @@
1
- # Openroad and QtCharts
2
-
3
- Tool: Graphical User Interface
4
-
5
- Subcategory: Library dependency issue
6
-
7
- ## Conversation
8
-
9
- ### pguerr91
10
- I installed openroad on RHEL8 using the documentation from GitHub. After launching openroad -gui, I noticed that it mentions QtCharts is not installed. So I built and compiled it (from source qtcharts-everywhere-src-5.15.0.zip), and and it appears to have installed in /usr/include/qt5/QtCharts ..but when I launch openroad -gui again , it STILL says "QtCharts not installed" ..(see attachment) Any ideas on what to do ?? This doesn't appear to be very straightforward
11
-
12
- ![openroad_QtCharts_missing](https://github.com/The-OpenROAD-Project/OpenROAD/assets/47336735/70f5288c-1aa8-447b-ac35-0c0cfb27bee0)
13
-
14
-
15
- ### maliberty
16
- Cmake does some caching so I suggest removing your build directory and re-running cmake to see if it then finds it.
17
-
18
- ### maliberty
19
- Is the rest of Qt installed in the same area?
20
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/1539.md DELETED
@@ -1,21 +0,0 @@
1
- # CTS Characterization
2
-
3
- Tool: Clock Tree Synthesis
4
-
5
- Subcategory: Customization request
6
-
7
- ## Conversation
8
-
9
- ### EffeErreG4
10
- I was trying to customize the CTS parameters using the command "configure_cts_characterization", but I don't see any changes is the maximum slew constrain reported in the .log file. Trying to understand if I was doing something wrong I noticed that there's a file called "CtsOptions.h" that should set the desired constrains with no "CtsOptions.cpp" file to describe the actual function. How can I manage to customize the maximum transition time? Thanks for your attention.
11
-
12
- ### maliberty
13
- All the functions are inlined so there is no need for a cpp.
14
-
15
- Would you give the command you are using and the message you are getting in the log.
16
-
17
- ### EffeErreG4
18
- Sorry if I made a silly observation.
19
- I was trying to define the maximum limits of slew and maybe I misunderstood the command.
20
- Is it possible to change the values of maximum slew and maximum skew constrain for the CTS synthesis?
21
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/1610.md DELETED
@@ -1,144 +0,0 @@
1
- # How to get heatmap data?
2
-
3
- Tool: Graphical User Interface
4
-
5
- Subcategory: Data extraction
6
-
7
- ## Conversation
8
-
9
- ### gudeh
10
- Hi guys, congratulations on all the great job done with the OpenROAD project!! I want to use it to develop my ideas during my Ph.D.
11
-
12
- I am trying to build a dataset for graph neural network training. My idea is to perform physical design predictions with a mapped circuit before P&R. I am trying to extract features from Verilog with Yosys, send them to the DGL python library and perform training with DGL. These steps are already operational, but I am missing an essential aspect of the prediction: the label!
13
-
14
- To solve the mentioned issue **I would like to have the data shown by the heatmaps in the GUI, such as placement density and routing congestion**. I would like them not as images but the actual numeric values. The positions of the cells and wires would also be essential.
15
-
16
- - Can anyone point me to which path I should go to get this data? I understand all of it is already processed by the code to show the images in the GUI. I just need to find it.
17
- - Would there be any TCL command which could help me with that?
18
- - Or my best shot is to try and use the odb database and edit some code?
19
-
20
- I noticed there are some heatmap codes in [./src/gui/src](https://github.com/The-OpenROAD-Project/OpenROAD/tree/master/src/gui/src), but there are so many attributes and methods. Also, I am not used to the odb database yet. Any help is welcome.
21
-
22
- ### gudeh
23
- By the way I couldn't find the path `./build/src/swig/tcl/opendbtcl` and `./build/src/swig/tcl/opendb_wrapper.cpp` as mentioned in [the documentation](https://openroad.readthedocs.io/en/latest/main/src/odb/README.html).
24
-
25
- ### maliberty
26
- The bit of documentation is out of date as we now include the tcl functionality in openroad itself and no longer build standalone executables for odb. (@vvbandeira)
27
-
28
- @arlpetergadfort My first thought was to look at each engine but maybe it would be easier to provide a dump_heatmap command in the GUI since it has already abstracted the interface to each engine. Does that seem reasonable to you?
29
-
30
- ### maliberty
31
- #1612 is merged so you should be good to go.
32
-
33
- ### maliberty
34
- You are repeating the previous rule and probably want something like:
35
-
36
- my_gui: my_gui_6_final.def
37
- $(foreach file,$(RESULTS_DEF),my_gui_$(file)): my_gui_%:
38
-
39
- You are getting the bbox of each instance. You'll have to map that back to the grid you are working with (an instance may be across a boundary as well).
40
-
41
- ### gudeh
42
- Hey guys, I have some issues with the heatmap features. I noticed that running the GCD project from a fresh OpenROAD-flow with this exact sequence of commands:
43
- ```
44
- git clone --recursive https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts.git
45
- cd OpenROAD-flow-scripts/
46
- sudo ./build_openroad.sh --local
47
- cd flow
48
- make
49
- make gui_final
50
- ```
51
- Renders no output on the circuit's image when clicking on the checkbox for `Placement Density`. The `Power Density` checkbox works fine. Furthermore, clicking on `Routing Congestion` and `IR Drop` gives the error message bellow and shows no heatmap in the image.
52
- ```
53
- [WARNING GUI-0066] Heat map "Routing Congestion" has not been populated with data.
54
- [WARNING GUI-0066] Heat map "IR Drop" has not been populated with data.
55
- ```
56
-
57
- If I run the AES project I can see the Placement and Power heatmaps. Although I have the same errors with Routing and IR Drop.
58
-
59
- The Routing and IR Drop also gives errors when trying to call gui::dump_heatmap: `[ERROR GUI-0072] "Routing Congestion" is not populated with data.`
60
- I also noticed that the CSVs provided by the gui::dump_heatmap command gives bouding boxes with different sizes for Placement and Power, is this expected?
61
-
62
-
63
- ### maliberty
64
- I don't see any issue with placement density. This is gcd/ng45:
65
- ![image](https://user-images.githubusercontent.com/761514/153918958-d33becda-6a06-417a-a685-463e6076575a.png)
66
-
67
-
68
- ### maliberty
69
- @arlpetergadfort I'm seeing:
70
- ```
71
- >>> read_guides results/nangate45/gcd/base/route.guide
72
- [WARNING GUI-0066] Heat map "Routing Congestion" has not been populated with data.
73
- ```
74
- This used to work - do you know what has changed?
75
-
76
- ### gudeh
77
- Hi again! I am progressing with my dataset generation. Looking real promising. I am only having issues trying to close the gui. Even if I use gui::hide it goes to the `openroad>` command option in terminal. How can I exit it the gui AND the openroad afterwards via a TCL file? [This is what I have tried](https://github.com/gudeh/OpenROAD-flow-scripts/blob/master/flow/scripts/getLabels.tcl). As seen in the last lines.
78
-
79
- By the way if you uncoment the part where I try to use the Routing and IRdrop heatmaps the gui::hide doesn't work.
80
-
81
- ### gudeh
82
-
83
-
84
- ### gudeh
85
- Hi everyone! I am coming back to this project. I was focusing on other tasks the last months.
86
-
87
- I wanted to share with you an example of what my code is able to generate by editing Yosys and OpenROAD: https://drive.google.com/drive/folders/1xTz4iTuGx0bDD-ZWAOV-MDQWKI0a8XA8?usp=sharing .
88
-
89
- This pair of CSV files can be used as input for DGL Python library and create a GNN.
90
-
91
- There is an issue though, I created a [Python script to check for collisions among the heatmaps and logic gate locations,](https://github.com/gudeh/OpenROAD-flow-scripts/blob/master/flow/myStuff/gateToHeat.py) and it is really slow. I made it by comparing the location of all the gates against each of the 4 heat types. I would like to ask any suggestions on how to improve this. Is this able to be solved on the OpenROAD db?
92
-
93
- ### maliberty
94
- The link to your script is broken. The heatmaps are a grid so it should be easy to compute the index into the map.
95
-
96
- Matt
97
-
98
- ### gudeh
99
- Hello again! I found a bug on my code to retrieve learning data using OpenROAD. The logic gate names don't match!
100
-
101
- My machine learning model features come from the verilog generated during the flow. Optionally I can use the 1_1_yosys.v ( post tech map ) or the 6_final.v ( post route ). Afterwards I get the labels using some TCL commands discussed previously in this post. For example:
102
-
103
-
104
- > set dut gatesPosition_
105
- > set fileName ${designPath}/${dut}${::env(DESIGN_NAME)}.csv
106
- > set outFile [open $fileName w]
107
- > puts $outFile "Name,xMin,yMin,xMax,yMax"
108
- > set block [ord::get_db_block]
109
- > foreach inst [$block getInsts] {
110
- > set box [$inst getBBox]
111
- > puts $outFile "[$inst getName], [ord::dbu_to_microns [$box xMin]], [ord::dbu_to_microns [$box yMin]], [ord::dbu_to_microns [$box xMax]], [ord::dbu_to_microns [$box yMax]]"
112
- > }
113
- > close $outFile
114
-
115
- At last, I have to build up my dataset by matching the logic gates names from the verilog, the logic gate names(from the TCL snippet pasted here and the heatmap dumps (positions). **But there is a problem:**
116
-
117
- I noticed that sometimes the flow changes the names of the gates between the verilog and the names retrieved from the TCL command ( `[$inst getName]`) causing unexpected behavior when I build the dataset. For example, the design bp_be_top with nangate45, there is a gate called `\be_calculator/_09864_` in the 6_final.v, and the name I get with the TCL command is `be_calculator/_09864_` without the `\`.
118
-
119
- **My question is:** Is there anyway to be sure that OR flow won't change the names of the gates? If not when and how does the tool changes the names of the gates, does it simply remove the starting `\` or are there any other possible modifications?
120
-
121
- ### gudeh
122
- Hi guys, I have another doubt regarding the heatmaps provided by OR. I would like to make sure the behavior is as intended. This is the routing congestion heatmap when executing the Rocket Tile design with standard values (config.mk) given by the repository:
123
- ![image](https://user-images.githubusercontent.com/37420320/230185344-17959d7b-05b3-4ee8-ab04-6865fb097f41.png)
124
-
125
- After executing the flow, OR inserts a lot of Filler Cells. It seems that the standard core size for Rocket Tile is extremely large, is there a reason for that?
126
-
127
- I ran the flow with the same design, although dividing the max X and max Y core area values in half and leaving the die area as is:
128
-
129
- > export DIE_AREA = 0 0 924.92 799.4
130
- > #export CORE_AREA = 10.07 9.8 914.85 789.6
131
- > export CORE_AREA = 10.07 9.8 457.425 394.8
132
-
133
- And this is the routing congestion heatmap after execution. There is still a considerably high congestion between core and die:
134
- ![image](https://user-images.githubusercontent.com/37420320/230186482-44fd0f4f-85d4-4fcc-afa1-ed0b05a1635d.png)
135
-
136
- To confirm, this is the placement density after the same run:
137
- ![image](https://user-images.githubusercontent.com/37420320/230188189-c3be97c8-c7a9-4f42-b78d-03918a202baf.png)
138
-
139
-
140
- This seems strange to me. I wouldn't expect so much routing congestion between die and core area. Furthermore, I couldn't even see metal wires on the green congested area. Is this as supposed to?
141
-
142
- ### gudeh
143
- Hello again. I wonder if there is a way to get the heatmaps considering only certain metal layers, is that possible?
144
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/1732.md DELETED
@@ -1,52 +0,0 @@
1
- # Can the grid/clips in the TritonRoute be exported?
2
-
3
- Tool: TritonRoute
4
-
5
- Subcategory: Information request
6
-
7
- ## Conversation
8
-
9
- ### Mohamed-Mejri
10
- Hello,
11
- I would like to know if the grid can be exported after the processing of the global router output and/or the TA step.
12
-
13
- I'm planning on trying some other AI based approaches instead of Heuristics. And if I can export the grid or the clips it would be more helpful.
14
-
15
- Any idea/help will be much appreciated!
16
-
17
- ### maliberty
18
- Do you mean the gcell grid? There are messages
19
-
20
- "GCELLGRID X {} DO {} STEP {} ;",
21
- "GCELLGRID Y {} DO {} STEP {} ;",
22
-
23
- that will give you those values. They don't change during drt.
24
-
25
- ### maliberty
26
- The post-processed guides are generated as output_guide.mod in ORFS (controlled by -output_guide). Other internal state of the router is not exported today.
27
-
28
- ### maliberty
29
- Its the same guide format as the input guide file
30
-
31
- ### Mohamed-Mejri
32
- Hello again,
33
- I would like to get the access points to each pin in a net and I saw [this on another discussion](https://github.com/The-OpenROAD-Project/OpenROAD/discussions/625?sort=new#discussioncomment-636424), however, when I tried it the coordinates didn't make sense.
34
- For example when I try it on the nangate45 gcd, for the _000_ net we have: `_000_ ( _672_ D ) ( _504_ ZN ) + USE SIGNAL`
35
- and the components in the net are `_672_ DFF_X2 + PLACED ( 107540 145600 ) N ;` and `_504_ OAI21_X1 + PLACED ( 107540 148400 ) FS ;`
36
- and this is the output of the code
37
- net _000_
38
- ( 46930 141260 ) layerNum 2 metal1
39
- ( 46930 141120 ) layerNum 2 metal1
40
- ( 46740 141260 ) layerNum 2 metal1
41
- ( 51490 146580 ) layerNum 2 metal1
42
- ( 51490 146860 ) layerNum 2 metal1
43
- ( 51490 147140 ) layerNum 2 metal1
44
- ( 51490 147420 ) layerNum 2 metal1
45
- ( 50730 147420 ) layerNum 2 metal1
46
- ( 51870 147420 ) layerNum 2 metal1
47
- ( 51870 147700 ) layerNum 2 metal1
48
- ( 51870 147980 ) layerNum 2 metal1
49
- ( 51110 147420 ) layerNum 2 metal1
50
-
51
- So from what I see these coordinates can't be correct, any idea why is this happening?
52
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/1870.md DELETED
@@ -1,20 +0,0 @@
1
- # Does detail router support spacing between different cut layers?
2
-
3
- Tool: Detailed Routing
4
-
5
- Subcategory: Tool capability
6
-
7
- ## Conversation
8
-
9
- ### davidcarails
10
- I have seen an example of a via/cut spacing rule between different layers.
11
- For example : v4 space v5 >= 38
12
- Can/does the detailed router support this?
13
-
14
- ### maliberty
15
- Its helpful to ask about a specific LEF rule but yes it does support cut spacing between layers.
16
-
17
- ### maliberty
18
- ![image](https://user-images.githubusercontent.com/761514/169117659-453ea3a8-10cb-4794-bb41-16558182e3f8.png)
19
-
20
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2083.md DELETED
@@ -1,93 +0,0 @@
1
- # How to contribute?
2
-
3
- Subcategory: Contribution inquiry
4
-
5
- ## Conversation
6
-
7
- ### niv280
8
- Hi, There is any way to contribute to the openRoad project?
9
-
10
- ### QuantamHD
11
- They accepted code changes through PRs.
12
-
13
- Is there something you are interested in working on?
14
-
15
- ### maliberty
16
- We are glad to have contributors. Do you want some suggestions or do you have something in mind?
17
-
18
- ### maliberty
19
- To help narrow it a bit are you more interested in development, testing, documentation, outreach? If you are willing to share a bit about yourself it would help to find a task of appropriate complexity.
20
-
21
- On the development side one idea that comes to mind is to improve write_abstract_lef written by @QuantamHD to give more precise obstructions. I can describe that further if it is of interest.
22
-
23
- ### maliberty
24
- The LEF abstract is a physical model of a block that is intended to be used at a higher level in the hierarchy to model the interface and obstructions in the block. The current code starts from https://github.com/The-OpenROAD-Project/OpenROAD/blob/c4a8479c341c31fd0db26a17f4a909f59285cf58/src/odb/src/lefout/lefout.cpp#L1213
25
-
26
- The current code is rather simplistic in its modeling of obstructions. If you look at lefout::getTechLayerObstructions it just gathers a set of layers that have any shapes on them and then blocks the entire layer.
27
-
28
- I think it would be better to use Boost polygon to OR together the shapes on each layer; do a bloat then shrink cycle to merge them into simpler shapes and then write out the result as the layer obstruction. The amount of bloating could be a user control with a reasonable default (say 2*pitch).
29
-
30
- The goal is to balance model size with precision. Does this make sense? I can go into more detail where needed.
31
-
32
- ### stefanottili
33
- Please keep in mind that there are two types of abstracts used by $$$ tools. The “cutout” where obstructions are cut out around pins and the “cover everything” where the pins are at the edges and the block is completely covered with obstruction. For the latter to work, the router has to be smart enough to route to covered pins and drc has to know that covered pins on the edge are ok too. It’s good practice to have pins on the edge of blocks anyways.
34
-
35
- ### maliberty
36
- You can see gcd_abstract* in https://github.com/The-OpenROAD-Project/OpenROAD/tree/master/src/odb/test for two examples.
37
-
38
- The idea of the bloat/shrink cycle is to merge nearby shapes. I've tried to quickly illustrate it with:
39
- ![image](https://user-images.githubusercontent.com/761514/180689779-273f4b34-d299-4251-a372-10437d7c246a.png)
40
-
41
- You can learn about Boost polygon at https://www.boost.org/doc/libs/1_79_0/libs/polygon/doc/index.htm (the docs aren't great).
42
-
43
- ### maliberty
44
- The red boxes in the middle image merge together into a single polygon
45
-
46
- ### niv280
47
- Hi, I will love to get some help in 2 issues.
48
- First I will need to import to boost::polygon library, in which file can I do it? Do other part of the code already import it?
49
-
50
- Second, I having trouble to understand how can I test my change, I gather all the shapes into kind of list and I now write it into the lef file instead the whole block boundary bbox, but I probably got some mistake so I want to run some test to debug it.
51
- There is any tutorial how can I do it?
52
-
53
- ### niv280
54
- Hi, So I make some progress with the abstract lef.
55
- But I encounter on some problem that I would like to get some help.
56
-
57
- So I modify the abstract lef that in order to write the merge between all the rect that intersect ( after bloat ).
58
- To demonstrate it I edit the picture from above:
59
-
60
- ![image](https://user-images.githubusercontent.com/61157132/186626392-73d8ee81-e11e-4ba1-8e75-b7668e319b47.png)
61
-
62
- The green rect is currently my OBS which isn't very efficient, but i didn't found any easy way to do it with the utils in the rect class.
63
-
64
- So I am guessing that I need to go back to your first suggestion which is use boost polygon to OR all the rect, my problem is that is after that I will need to convert it back into different rects, there is any easy way to do that?
65
-
66
-
67
-
68
- ### stefanottili
69
- https://www.boost.org/doc/libs/1_79_0/libs/polygon/doc/gtl_polygon_90_set_concept.htm
70
-
71
- Have a look at get_rectangles and get_max_rectangles
72
-
73
- On Aug 25, 2022, at 02:20, niv280 ***@***.***> wrote:
74
-
75
- 
76
- Hi, So I make some progress with the abstract lef.
77
- But I encounter on some problem that I would like to get some help.
78
-
79
- So I modify the abstract lef that contained the merge between all the rect that intersect.
80
- To demonstrate I edit the picture above:
81
-
82
-
83
-
84
- The green rect is currently my OBS which isn't very efficient, but i didn't found any easy way to do it with the utils in the rect class.
85
- So I am guessing that I need to go back to your first suggestion which is use boost polygon to OR all the rect, my problem is that is after that I will need to convert is back into different rects, there is any easy way to do that?
86
-
87
-
88
- Reply to this email directly, view it on GitHub, or unsubscribe.
89
- You are receiving this because you commented.
90
-
91
- ### maliberty
92
- get_rectangles would be the better choice as get_max_rectangles may produce overlapping rectangles. You an experiment with the slicing direction to see what produces a more minimal result. My guess is the non-preferred routing direction will work best.
93
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2745.md DELETED
@@ -1,305 +0,0 @@
1
- # Options in the Python API
2
-
3
- Tool: Global Placement
4
-
5
- Subcategory: Usage question
6
-
7
- ## Conversation
8
-
9
- ### maliberty
10
- The python api differs from tcl in being more OO (objects/methods) rather than command oriented. I'd like to discuss standardizing how that API accept options. Current APIs are variable:
11
- - Some use state building commands. For example pdn has define_pdn_grid, add_pdn_stripe, etc.
12
- - Some persistently hold an options object that can be modified by the user. For example TritonCTS::getParms()
13
- - Some take their options as arguments. For example Resizer::repairHold(...)
14
-
15
- Complicating cases are:
16
- - Tools that call other tools. For example gpl calls grt and rsz
17
- - Incremental operations that retain state between invocations. For example grt and sta
18
-
19
- My best thought on how to standardize is to have a persistent set of default options and the ability to pass an overriding set. A sketch of the idea:
20
- ```
21
- class ToolOptions
22
- {
23
- public:
24
- ToolOptions(); // a well-defined default state
25
- void setOptionA(int value);
26
- void setOptionB(bool value);
27
- };
28
-
29
- class Tool
30
- {
31
- public:
32
- static ToolOptions* getDefaultOptions();
33
-
34
- // if options is nullptr then the default options are used.
35
- void task(ToolOptions* options = nullptr);
36
-
37
- private:
38
- static ToolOptions* default_options_;
39
- };
40
- ```
41
-
42
- One use model would be pre-configuration (in C++ but similarly in python)
43
- ```
44
- // setup
45
- auto default_options = Tool::getDefaultOptions();
46
- default_options.setOptionB(false);
47
-
48
- // later
49
- tool->task();
50
- ```
51
-
52
- Another use model could be
53
- ```
54
- ToolOptions options;
55
- options.setOptionB(false);
56
- tool->task(options);
57
- ```
58
-
59
- This can be extended to the case of one tool calling another internally with an API like:
60
- ```
61
- void task(ToolOptions* options = nullptr,
62
- AnotherToolOptions* options = nullptr);
63
- ```
64
-
65
- For a sufficiently complicated tool the options object could itself become a sub-configuration builder. For example:
66
- ```
67
- class PdnOptions
68
- {
69
- public:
70
- RingOptions* add_ring();
71
- };
72
- ```
73
-
74
- The case of an incremental tool is tricky. If asked to do an update I think it should do so according to the last set of options (default or not) that it used. This implies that it must keep a copy of any non-default options object.
75
-
76
- I'm open to other ideas or improvements. I'd love to hear from folks @gadfort @macd @QuantamHD @cdleary @osamahammad21 @antonblanchard @donn @rovinski
77
-
78
- ### maliberty
79
- @proppy
80
-
81
- ### QuantamHD
82
- I like the idea, but I think I would make a modification to a builder architecture, which I think makes sense for two reasons.
83
-
84
- 1. It allows you to do more validation in your builder which would give us the ability ensure that a user can never create an invalid tool configuration. For example creating a PDN that has straps repeat at a greater pitch than the width of the chip (Which I've run into)
85
- 2. I like the idea of `ToolOptions` being an Immutable object. It means that a tool cannot modify the options which I think reduces the possibility of tools doing weird things with user provided options.
86
-
87
- ```c++
88
- class ToolOptionsBuilder : OptionBuilder {
89
- public:
90
- /*
91
- * Not necessarily required in all cases, but could help build default options for a particular PDK, or
92
- * core size etc.
93
- */
94
- ToolOptionsBuilder(Design *);
95
-
96
- void setOptionA(int A);
97
- void setOptionB(bool B);
98
- ErrorOr<ToolOptions> create(); // could also throw an exception.
99
- }
100
-
101
- class ToolOptions : ToolOption{
102
- private:
103
- ToolOptions(int A, bool B); // a well-defined default state
104
-
105
- public:
106
- int getOptionA();
107
- bool getOptionB();
108
- };
109
-
110
- class Tool {
111
- public:
112
- static ToolOptions* getDefaultOptions(); // calls ToolOptionsBuilder(...).create();
113
-
114
- // if options is nullptr then the default options are used.
115
- void task(ToolOptions* options = nullptr);
116
- };
117
- ```
118
-
119
-
120
-
121
- > ```c++
122
- > // setup
123
- > auto default_options = Tool::getDefaultOptions();
124
- > default_options.setOptionB(false);
125
- >
126
- > // later
127
- > tool->task();
128
- > ```
129
- I don't like the idea of modifying the default options object, seems very error prone.
130
-
131
-
132
-
133
- > Another use model could be
134
- >
135
- > ```c++
136
- > ToolOptionsBuilder options;
137
- > options.setOptionB(false);
138
- > tool->task(options.create());
139
- > ```
140
- I like this model, but with the builder pattern.
141
-
142
-
143
- > This can be extended to the case of one tool calling another internally with an API like:
144
- >
145
- > ```c++
146
- > void task(ToolOptions* options = nullptr,
147
- > AnotherToolOptions* options = nullptr);
148
- > ```
149
- I think this is a greate idea too.
150
-
151
-
152
- > For a sufficiently complicated tool the options object could itself become a sub-configuration builder. For example:
153
- >
154
- > ```c++
155
- > class PdnOptions
156
- > {
157
- > public:
158
- > RingOptions* getRing();
159
- > };
160
- > ```
161
- I like this but again should be constructed using builders.
162
-
163
-
164
- > The case of an incremental tool is tricky. If asked to do an update I think it should do so according to the last set of options (default or not) that it used. This implies that it must keep a copy of any non-default options object.
165
-
166
- I think there's also another problem
167
- 1. The common use mode of the tools is to do one step then dump an ODB file. I don't think we can get rid of this use mode, because then it would be impossible to run the tool incrementally. Which is making me feel like we need to serialize them into the database.
168
-
169
- I've thought about it a bunch, and I think storing a hidden only history from a user is probably not the right API instead I suggest.
170
-
171
- ```c++
172
- class Tool {
173
- public:
174
- static ToolOptions* getDefaultOptions(); // calls ToolOptionsBuilder(...).create();
175
- set incrementalOptions(ToolOptions* options);
176
-
177
- // if options is nullptr then the default options are used.
178
- void task(ToolOptions* options = nullptr);
179
-
180
- private:
181
- ToolOptions* incremental_options_;
182
-
183
- };
184
- ```
185
-
186
- On construction the incrementalOptions are set to what's provided in the constructor, or can be updated by the user.
187
-
188
- This brings up another question about incremental APIs. @maliberty how do you envision a tool getting access to a `Tool` object will the user need to pass one into the options, or something else?
189
-
190
-
191
- ### rovinski
192
- It's a very interesting question and I feel like I've become jaded because of how inconsistent commercial tools are. It seems like tools (both commercial and OpenROAD) always consist of some combination of the three options you mentioned. What's worse is that commercial tools can be some kind of weird blend of global variables, app variables, tool variables, etc. all with different methods for accessing them... it can get overwhelming.
193
-
194
- I think for the most part, I like the idea of doing away with arguments to commands and having all options passed through some kind of options object. The caveat is that I am split on whether that's appropriate for very simple commands that only take one parameter, like `read_odb [filename]`.
195
-
196
- Whatever the decision is, I _definitely_ want to see a common command / interface that lets a user easily query all parameters that can be set for a tool. For example:
197
- ```
198
- openroad> list_parameters Tool
199
- Parameters for command 'Tool':
200
- Parameter Type Value Default Description
201
- -------------------------------------------
202
- A int 1 1 Short description of A
203
- B bool 1 0 Short description of B
204
- -------------------------------------------
205
- Use 'help Tool' for more information on this command's parameters
206
-
207
- openroad> help Tool
208
- Parameter Definition
209
- ------------------------
210
- A This is a long-form description of A. Here are the valid values, maybe some tips, etc.
211
- The description could be multiple lines.
212
-
213
- B This is a long-form description of B. Here are the valid values, maybe some tips, etc.
214
-
215
- Use 'list_parameters Tool' to list the current values for this command's parameters
216
- ```
217
-
218
- Hidden state / parameters is one of the things I hate the most about commercial tools. At the same time, a user definitely shouldn't _need_ to set parameters they don't know about, like bin grid size for GPL.
219
-
220
- These comments are mostly concerning the user-side interface. As for the developer / C++ API, I don't think I have strong opinions. I think the proposed interface sounds ok.
221
-
222
- ### maliberty
223
- I'm lukewarm on a builder. Your two arguments for it were:
224
-
225
- "It allows you to do more validation in your builder". You can just as easily do this validation in the task. If you want to do it in the builder then you will have to restrict when it can be used (ie not before the db is populated) which seems awkward. The builder itself will have to be constructed by the tool to give it enough state for validation.
226
-
227
- "I like the idea of ToolOptions being an Immutable object. It means that a tool cannot modify the options which I think reduces the possibility of tools doing weird things with user provided options." I see two problems. The tool can always clone the options object and do "weird things". In gpl for example we set options before calling grt (see https://github.com/The-OpenROAD-Project/OpenROAD/blob/b632f9f5177bc27fe7323beb1e5a97a8c904ccee/src/gpl/src/routeBase.cpp#L374). I wouldn't want to force the user to know to do so.
228
-
229
- ### maliberty
230
- re "I don't like the idea of modifying the default options object, seems very error prone."
231
-
232
- I have a somewhat similar feeling but I'm also afraid of producing very complex API calls (eg gpl). I think some people would prefer to setup the tools upfront. Also interactively it will save a lot of typing. However I am fine to remove it if there is a consensus that it isn't useful.
233
-
234
- ### maliberty
235
- Putting the options in the db will open it up to tons of schema updates which is undesirable. Or we would have to make the storage extremely generic which will push the validation on load problem to each tool which isn't much better. Its also error prone for the user.
236
-
237
- I lean toward saying that on reload you don't get any incremental operations. We are living with that today, sta is not incremental across restart.
238
-
239
- ### donn
240
- Sorry it's taken me a minute to respond to this- perhaps I can offer a bit of a different perspective being more on the user side, but:
241
-
242
- * Lukewarm on the builder, too. I don't see the utility outside of a niche case where I may elect to build and serialize the options in OpenLane then use it in OpenROAD, but I'm fairly sure that won't be possible regardless.
243
- * I like the idea of immutability vs. modifying a global variable. I get that means more typing, but I think it's worth it just to have less surprises. i.e. I wholeheartedly endorse this model:
244
- ```c++
245
- ToolOptions options;
246
- options.setOptionB(false);
247
- tool->task(options);
248
- ```
249
-
250
- From where I stand, the above model would let me write a single common file to convert OpenLane variables to an OpenROAD ToolOptions object generator, which can then be passed onto other tools.
251
-
252
- ### maliberty
253
- @rovinski tcl is a completely different API with lots of manual coding. Converting it look like python, if possible, would introduce the same friction of it looking nothing like usual EDA tools' tcl interface. I don't think it is worth the effort to maintain two sets of APIs. Klayout supporting both python & ruby is much simpler since they are both OO languages. We could do that too more easily (though I have no desire to).
254
-
255
- ### maliberty
256
- Based on the discussions I'm wondering if it is preferrable to eliminate the global state and use only explicit options with a default arg:
257
- ```
258
- class Tool
259
- {
260
- public:
261
- void task(const ToolOptions& options = ToolOptions());
262
- void complex_task(const ToolOptions& options = ToolOptions(),
263
- const AnotherToolOptions& other_options = AnotherToolOptions());
264
- };
265
- ```
266
-
267
- ### donn
268
- Should probably add- syntactic sugar in the form of
269
-
270
- ```c++
271
- auto options = ToolOptions {
272
- {"a", "value1"},
273
- {"b", "value2"}
274
- };
275
- ```
276
-
277
- i.e., one that basically takes a dict, with the appropriate bridging to python:
278
-
279
- ```python
280
- options = ToolOptions(
281
- a="value1",
282
- b="value2",
283
- )
284
- ```
285
-
286
- would be pretty cool
287
-
288
- ### maliberty
289
- For a next step I want to make a concrete example. Looking at gpl it fits this model well is it is a single task (placement) with many options.
290
-
291
- When I look at ifp it is more problematic. It is a tool with multiple semi-related tasks: initFloorplan, insertTieCells, and makeTracks. I don't feel it makes sense to have a single options object to cover such diverse tasks. Perhaps this would be better formulated as TaskOptions rather than ToolOptions. A TaskOptions could replace the need for overloaded methods.
292
-
293
- This does run the risk of a proliferation of classes - worst case is one for every method. I am hopeful that the number of tasks is fairly limited per tool today.
294
-
295
- ### maliberty
296
- I created https://github.com/The-OpenROAD-Project/OpenROAD/pull/2809 as a example of what the revised API for gpl could look like. The user tcl layer is unchanged but python and c++ see a new options object. Replace has way too many options so it produces a very large object interface.
297
-
298
- Having made the change I'm a bit on the fence about keeping it like this versus making either (1) a code generator from a description file or (2) a more weakly typed interface using string (or enum) keys with a variant value and a single get/set method. I'm glad to hear opinions.
299
-
300
- ### maliberty
301
- Any thoughts on either the existing approach or my other suggestion?
302
-
303
- ### maliberty
304
- I came across https://abseil.io/tips/173 which gives some nice ideas for using designated initializers
305
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2800.md DELETED
@@ -1,24 +0,0 @@
1
- # [developer docs] Errors thrown in C++ test files?
2
-
3
- Subcategory: Best practices
4
-
5
- ## Conversation
6
-
7
- ### cdleary
8
- I presume for errors in C++ test code (e.g. fixtures and similar) it's ok to throw more "bare" errors (vs the scheme used with the logger and explicitly enumerated exceptions) -- that is, it's ok to throw a derived class from `std::runtime_error` if something goes wrong in test fixture scaffolding?
9
-
10
- If so I'll update the developer docs with a small note, but I wanted to check this seemed ok.
11
-
12
- CC @maliberty
13
-
14
- ### cdleary
15
- (Or if non-exception-code is preferred in test code, that'd be fine too, just let me know what the preferred way to fatal-error-with-message would be.)
16
-
17
- ### cdleary
18
- (Or possibly we use logger with an error ID of 0 for a testing use cases like this?)
19
-
20
- Apologies for the stream of conscious of possibilities. :-)
21
-
22
- ### maliberty
23
- What do you mean by "explicitly enumerated exceptions"? In general I'm ok with your initial statement.
24
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2868.md DELETED
@@ -1,130 +0,0 @@
1
- # How do I figure out valid macro coordinates for manual placement?
2
-
3
- Tool: Initialize Floorplan
4
-
5
- Subcategory: Macro placement
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- I'm trying to find out valid coordinates to put macros onto. The pins of the macros must align on the routing grid.
11
-
12
- From ASAP 7 LEF files, I see that pins are on M4 and M5 layer. From make_tracks.tcl, I see offsets and pitches.
13
-
14
- From that information, I should be able to come up with some formulae of valid macro positions....
15
-
16
- I just seem to be unable to connect the dots here to what the formulae should be:
17
-
18
- M4 is horizontal pins and M5 is vertical pins (or vice versa, I could see in the GUI, but I don't know how to tell from the LEF file):
19
-
20
-
21
- The pins are from a macro, so I know the pin coordinates below are correct:
22
-
23
- ```
24
- PIN foo[50]
25
- DIRECTION INPUT ;
26
- USE SIGNAL ;
27
- PORT
28
- LAYER M4 ;
29
- RECT 144.818 86.208 145.152 86.232 ;
30
- END
31
- END foo[50]
32
-
33
- PIN bar
34
- DIRECTION INPUT ;
35
- USE SIGNAL ;
36
- PORT
37
- LAYER M5 ;
38
- RECT 101.76 144.818 101.784 145.152 ;
39
- END
40
- END bar
41
- ```
42
-
43
- from make_tracks.tcl:
44
-
45
- ```
46
- make_tracks M4 -x_offset [expr 0.009 * $multiplier] -x_pitch [expr 0.036 * $multiplier] -y_offset [expr 0.012 * $multiplier] -y_pitch [expr 0.048 * $multiplier]
47
- make_tracks M5 -x_offset [expr 0.012 * $multiplier] -x_pitch [expr 0.048 * $multiplier] -y_offset [expr 0.012 * $multiplier] -y_pitch [expr 0.048 * $multiplier]
48
- ```
49
-
50
-
51
- ### yupferris
52
- @maliberty mentioned in our discussion yesterday that the routing grid is defined in the tech lef for the PDK. For ASAP7 we have to look at the [generated tech lef in ORFS](https://github.com/The-OpenROAD-Project/asap7/issues/19#issuecomment-1115712485) which should be `OpenROAD-flow-scripts/flow/platforms/asap7/lef/asap7_tech_1x_201209.lef`:
53
-
54
- ```
55
- LAYER M4
56
- TYPE ROUTING ;
57
- DIRECTION HORIZONTAL ;
58
- PITCH 0.048 ;
59
- WIDTH 0.024 ;
60
- SPACING 0.024 ;
61
-
62
- OFFSET 0.003 ;
63
-
64
- AREA 0.008 ;
65
-
66
- PROPERTY LEF58_SPACING "
67
- SPACING 0.024 ENDOFLINE 0.025 WITHIN 0.04 ENDTOEND 0.04 ; " ;
68
-
69
- PROPERTY LEF58_WIDTHTABLE
70
- " WIDTHTABLE 0.024 0.12 0.216 0.312 0.408 ; " ;
71
-
72
- PROPERTY LEF58_CORNERSPACING "
73
- CORNERSPACING CONVEXCORNER CORNERONLY 0.048
74
- WIDTH 0.0 SPACING 0.04 ;
75
- " ;
76
-
77
- PROPERTY LEF58_EOLKEEPOUT "
78
- EOLKEEPOUT 0.025 EXTENSION 0.048 0.02425 0.048 CORNERONLY ;
79
- " ;
80
-
81
- # spacing table is required for the rule that has wide metal requires a 72nm (288 scaled)
82
- # spacing between wide and minimum metals
83
-
84
- SPACINGTABLE
85
- PARALLELRUNLENGTH 0.0
86
- WIDTH 0.0 0.024
87
- WIDTH 0.025 0.072 ;
88
-
89
- PROPERTY LEF58_RIGHTWAYONGRIDONLY "
90
- RIGHTWAYONGRIDONLY ;
91
- " ;
92
-
93
- PROPERTY LEF58_RECTONLY "
94
- RECTONLY ;
95
- " ;
96
-
97
- END M4
98
- ```
99
-
100
- From this we can indeed see that M4 is horizontal and M5 is vertical (not shown above but the definitions for M5 are below those for M4 in the file). We can also see that the pitch is `0.048` which lines up with the `-y_pitch` arg in the `make_tracks.tcl` code above, among other things. However, I'm also a bit confused at how to use this information.
101
-
102
- Some specific questions:
103
-
104
- - Where does `0.012` for the `-y_offset` arg in `make_tracks.tcl` come from? I would have assumed it would be `0.003` from the `OFFSET` in the tech lef.
105
- - How does offset/pitch relate to macro position? I would assume that the bottom-left of a macro is the origin (0, 0), and that if we respect `PITCH` and `OFFSET` from the tech lef above for IO y-positions (eg. `my_io_y = OFFSET + some_integer * PITCH`) we can then place that macro at a position which ensures those constraints are still respected (eg. `my_macro_y = some_integer * PITCH - OFFSET`). Is this correct?
106
-
107
- "Bonus" question: What's the difference between the 1x and 4x .lef files in the PDK?
108
-
109
-
110
- ### maliberty
111
- In the LEF you can see the preferred routing direction from:
112
- ```
113
- LAYER M4
114
- DIRECTION HORIZONTAL ;
115
-
116
- LAYER M5
117
- DIRECTION VERTICAL ;
118
- ```
119
-
120
- If you look at M1 you'll see it has an offset of 0 which makes the first track unusable (a wire would be half outside the bounds if that track were used). So in make_tracks it was setup to make the first track usable by using a 1/2 width offset. Similarly the other layers need adjusting. Its mostly a matter of style and either could have been used.
121
-
122
- M2 has a track pattern too complex to express in the LEF format so make_tracks.tcl is required in any case.
123
-
124
- If you place a macro a (0,0) the tracks should align since they would be built the way way. Moving the macro by a multiple of the pitch should keep it aligned. You would use the m4 pitch vertically and the m5 pitch horizontally.
125
-
126
- You can check your work by turning on m4 & m5 visibility in the GUI, turning on the display of the preferred tracks and look at your pins to see that the tracks go through the center.
127
-
128
- ### maliberty
129
- Bonus: 1X and 4X can be ignored as OR is only using 1X. The origin is that some academic users may not have the advanced node licenses for proprietary tools required to use a 7nm process. The 4X library makes it appear like a 28nm library by making all dimensions 4X larger as a workaround. Since OR has no licensing 4X is not required.
130
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2923.md DELETED
@@ -1,55 +0,0 @@
1
- # Using a regex for set_io_pin_constraint -names
2
-
3
- Tool: Pin Placer
4
-
5
- Subcategory: Usage question
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- How can I get a list of the names of the pins, such that I can pass in a list of names to set_io_pin_constraint that match a regex?
11
-
12
- Something like:
13
-
14
- ```
15
- set_io_pin_constraint ... -names [lsearch -all -inline $pins $regex]
16
- ```
17
-
18
- Answering myself..
19
-
20
- This will do it:
21
-
22
- ```
23
- proc match_pins { regex } {
24
- set pins {}
25
- foreach pin [sta::find_port_pins_matching $regex 1 0] {
26
- lappend pins [get_property $pin name]
27
- }
28
- return $pins
29
- }
30
-
31
- set_io_pin_constraint -region top:* -pin_names [match_pins someregex]
32
- ```
33
-
34
-
35
- ### maliberty
36
- See discussion in https://github.com/The-OpenROAD-Project/OpenROAD/pull/2839
37
-
38
- ### maliberty
39
- The point being there isn't a default mechanism right now but rather a discussion of how best to do it. get_pins will return a list of pins objects rather than names. You could convert them to names or you could use the odb APIs to traverse the db yourself.
40
-
41
- ### oharboe
42
- This will do it:
43
-
44
- ```
45
- set_io_pin_constraint ... -names [sta::find_port_pins_matching $regex 1 0]
46
- ```
47
-
48
-
49
-
50
- ### maliberty
51
- What do you mean by "verilog pin names"? Those look ok to me for instance pins
52
-
53
- ### maliberty
54
- Perhaps you want get_ports? I would call those port names as Verilog includes the instance pins as well.
55
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2927.md DELETED
@@ -1,22 +0,0 @@
1
- # Iterating on top level floorplan with macro pin constraints
2
-
3
- Tool: Initialize Floorplan
4
-
5
- Subcategory: Flow customization
6
-
7
- ## Conversation
8
-
9
- ### oharboe
10
- I would like to iterate on the floorplan of the top level of our design. In doing so, I want to change the pin constraints for the macros used at the top level.
11
-
12
- However, ```make generate_abstract``` goes all the way to detailed routing before producing a .gds, .lef and .lib file. This takes a long time.
13
-
14
- Is there a way to run generate_abstract after IO pin placement on the macro without going through detailed route?
15
-
16
-
17
- ### maliberty
18
- The flow itself doesn't have a mechanism but the command should work at that point (though it hasn't been tested). You could add a flow option if needed.
19
-
20
- ### oharboe
21
- Solution implemented: `make skip_cts skip_route generate_abstract`
22
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/2965.md DELETED
@@ -1,33 +0,0 @@
1
- # Open a sample project in the OpenROAD GUI
2
-
3
- Tool: Graphical User Interface
4
-
5
- Subcategory: Usage question
6
-
7
- ## Conversation
8
-
9
- ### vic4key
10
- Hi everybody,
11
-
12
- I already build OpenROAD GUI to run on Ubuntu Linux. Now I'm looking for a sample project that can open directly via main menu `File > Open DB` in OpenROAD GUI (like the below image), I have spent a lot of time to find the way (reading read-me, watching video, etc) to do it, but I did not complete.
13
- I found a data test at https://github.com/TILOS-AI-Institute/MacroPlacement/tree/main/Flows/NanGate45/ariane133 but seems it cannot open directly by OpenROAD and maybe need to do several pre-processing steps before can open in OpenROAD GUI.
14
- Could you please help me to know how to do it or give me detail instructions to open this test data in the OpenROAD GUI?
15
- Thanks.
16
-
17
- ![sample](https://user-images.githubusercontent.com/5672864/222308822-2fc0204a-440c-4593-a04b-a4e82f591073.png)
18
-
19
-
20
- ### QuantamHD
21
- Hi @vic4key,
22
-
23
- It's not clear what's failing, and what you would like to see? It would also be helpful if you uploaded the data you could upload your test data in a zip folder and post it here. So that we can debug th issue.
24
-
25
- ### vijayank88
26
- @vic4key
27
- Same design implemented in OpenROAD-flow-scripts. https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/tree/master/flow/designs/nangate45/ariane136
28
- All you need to install OpenROAD-flow-scripts and run the design and view it in OpenROAD GUI.
29
- Installation document available here: https://openroad-flow-scripts.readthedocs.io/en/latest/user/BuildLocally.html
30
-
31
- ### maliberty
32
- cuda will make almost no difference to runtime. I would start by running gcd as it is the smallest test case.
33
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gh_discussions/Query/3023.md DELETED
@@ -1,18 +0,0 @@
1
- # Clock Division
2
-
3
- Tool: OpenSTA
4
-
5
- Subcategory: Constraint definition
6
-
7
- ## Conversation
8
-
9
- ### Ziad-cyber
10
- How to define a constraint on a generated clock that's divided by 2 from a master clock source?
11
-
12
- ### vijayank88
13
- OpenROAD flow accepts all standard SDC formats. Just browse it and implement the same.
14
- OpenSTA doc found [here](https://github.com/The-OpenROAD-Project/OpenSTA/blob/master/doc/OpenSTA.pdf)
15
-
16
- ### maliberty
17
- In particular see create_generated_clock
18
-