You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.developers.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
For general guidance on contributing to VTR see [Submitting Code to VTR](CONTRIBUTING.md#submitting-code-to-vtr).
4
4
5
-
The actual machanics of submitting code are outlined below.
5
+
The actual mechanics of submitting code are outlined below.
6
6
7
7
However they differ slightly depending on whether you are:
8
8
* an **internal developer** (i.e. you have commit access to the main VTR repository at `github.com/verilog-to-routing/vtr-verilog-to-routing`) or,
@@ -149,7 +149,7 @@ To provide quick context, some VTR developers also tag the first line with the m
149
149
## Commit Structure
150
150
Generally, you should strive to keep commits atomic (i.e. they do one logical change to the code).
151
151
This often means keeping commits small and focused in what they change.
152
-
Of course, a large number of miniscule commits is also unhelpful (overwhelming and difficult to see the structure), and sometimes things can only be done in large changes -- so use your judgement.
152
+
Of course, a large number of minuscule commits is also unhelpful (overwhelming and difficult to see the structure), and sometimes things can only be done in large changes -- so use your judgement.
153
153
A reasonable rule of thumb is to try and ensure VTR will still compile after each commit.
154
154
155
155
For those familiar with history re-writing features in git (e.g. rebase) you can sometimes use these to clean-up your commit history after the fact.
NoC benchmarks currently include synthetic and MLP benchmarks. Synthetic benchmarks have various NoC traffic patters,
630
+
NoC benchmarks currently include synthetic and MLP benchmarks. Synthetic benchmarks have various NoC traffic patterns,
631
631
bandwidth utilization, and latency requirements. High-quality NoC router placement solutions for these benchmarks are
632
632
known. By comparing the known solutions with NoC router placement results, the developer can evaluate the sanity of
633
633
the NoC router placement algorithm. MLP benchmarks are the only realistic netlists included in this benchmark set.
@@ -702,7 +702,7 @@ The following table provides details on available Koios settings in VTR flow:
702
702
703
703
For more information refer to the [Koios benchmark home page](vtr_flow/benchmarks/verilog/koios/README.md).
704
704
705
-
To make running all the koios benchmarks easier, especially with thos circuits scattered between different tasks, there is an overall task list that runs all the 40 circuits of Koios as follows (this will run all the circuits with complex DSP functionality enabled. If you want to disable the complex DSP, edit the file to point to the `koios_*_no_hb` tasks):
705
+
To make running all the koios benchmarks easier, especially with those circuits scattered between different tasks, there is an overall task list that runs all the 40 circuits of Koios as follows (this will run all the circuits with complex DSP functionality enabled. If you want to disable the complex DSP, edit the file to point to the `koios_*_no_hb` tasks):
Copy file name to clipboardExpand all lines: cmake/toolchains/mingw-linux-cross-compile-to-windows.cmake
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,17 @@
1
1
# the name of the target operating system
2
2
SET(CMAKE_SYSTEM_NAME Windows)
3
3
4
-
option(STATIC_LIBGCC_LIBSTDCPP "Link to libgcc and libstdc++ statically. If not set, requires libgcc and libstdc++ DLLs to be installed on the target machines. Note that static linking libgcc means exceptions will not propagate accross shared library boundaries."OFF)
4
+
option(STATIC_LIBGCC_LIBSTDCPP "Link to libgcc and libstdc++ statically. If not set, requires libgcc and libstdc++ DLLs to be installed on the target machines. Note that static linking libgcc means exceptions will not propagate across shared library boundaries."OFF)
5
5
6
6
#Note that if libgcc and libstdcpp are NOT statically linked the appropriate
7
7
#DLL's should be installed on the target Windows machine, or distributed with
8
-
#the generated executables (e.g. in the same directory as the exectuable).
8
+
#the generated executables (e.g. in the same directory as the executable).
0 commit comments