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
@@ -122,10 +122,6 @@ When compiling for FPGA hardware, it is recommended to increase the job timeout
122
122
```
123
123
make report
124
124
```
125
-
* Compile for simulation (fast compile time, targets simulated FPGA device, reduced data size):
126
-
```
127
-
make fpga_sim
128
-
```
129
125
* Compile for FPGA hardware (longer compile time, targets FPGA device):
130
126
```
131
127
make fpga
@@ -163,10 +159,6 @@ When compiling for FPGA hardware, it is recommended to increase the job timeout
163
159
```
164
160
nmake report
165
161
```
166
-
* Compile for simulation (fast compile time, targets simulated FPGA device, reduced data size):
167
-
```
168
-
nmake fpga_sim
169
-
```
170
162
* Compile for FPGA hardware (longer compile time, targets FPGA device):
171
163
```
172
164
nmake fpga
@@ -202,12 +194,7 @@ On the main report page, scroll down to the section titled "Estimated Resource U
202
194
./private_copies.fpga_emu (Linux)
203
195
private_copies.fpga_emu.exe (Windows)
204
196
```
205
-
2. Run the sample on the FPGA simulator device:
206
-
```
207
-
./private_copies.fpga (Linux)
208
-
private_copies.fpga.exe (Windows)
209
-
```
210
-
3. Run the sample on the FPGA device:
197
+
2. Run the sample on the FPGA device:
211
198
```
212
199
./private_copies.fpga (Linux)
213
200
private_copies.fpga.exe (Windows)
@@ -238,7 +225,7 @@ When run on the Intel® PAC with Intel Arria10® 10 GX FPGA hardware board
238
225
239
226
Setting the `private_copies` attribute to 0 (or equivalently omitting the attribute entirely) produced good throughput, and the reports show us that the compiler selected 3 private copies. This does produce the optimal throughput, but in this case it probably makes sense to save some area in exchange for a very small throughput loss by specifying 2 private copies instead.
240
227
241
-
When run on the FPGA emulator or simulator, the `private_copies` attribute has no effect on kernel time. You may actually notice that the emulator achieved higher throughput than the FPGA in this example. This is because this trivial example uses only a tiny fraction of the spatial compute resources available on the FPGA.
228
+
When run on the FPGA emulator, the `private_copies` attribute has no effect on kernel time. You may actually notice that the emulator achieved higher throughput than the FPGA in this example. This is because this trivial example uses only a tiny fraction of the spatial compute resources available on the FPGA.
242
229
243
230
## License
244
231
Code samples are licensed under the MIT license. See
0 commit comments