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
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -151,7 +151,7 @@ The design uses the following generic header files.
151
151
### On Linux*
152
152
153
153
1. Change to the sample directory.
154
-
2. Configure the build system for the Agilex™ device family, which is the default.
154
+
2. Configure the build system for the Agilex® device family, which is the default.
155
155
156
156
```
157
157
mkdir build
@@ -195,7 +195,7 @@ The design uses the following generic header files.
195
195
### On Windows*
196
196
197
197
1. Change to the sample directory.
198
-
2. Configure the build system for the Agilex™ device family, which is the default.
198
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -122,7 +122,7 @@ Performance results are based on testing as of Jan 31, 2022.
122
122
### On Linux*
123
123
124
124
1. Change to the sample directory.
125
-
2. Configure the build system for the Agilex™ device family, which is the default.
125
+
2. Configure the build system for the Agilex® device family, which is the default.
126
126
127
127
```
128
128
mkdir build
@@ -162,7 +162,7 @@ Performance results are based on testing as of Jan 31, 2022.
162
162
### On Windows*
163
163
164
164
1. Change to the sample directory.
165
-
2. Configure the build system for the Agilex™ device family, which is the default.
165
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -143,7 +143,7 @@ For `constexpr_math.hpp`, `memory_utils.hpp`, `metaprogramming_utils.hpp`, and `
143
143
### On Linux*
144
144
145
145
1. Change to the sample directory.
146
-
2. Configure the build system for the Agilex™ device family, which is the default.
146
+
2. Configure the build system for the Agilex® device family, which is the default.
147
147
148
148
```
149
149
mkdir build
@@ -187,7 +187,7 @@ For `constexpr_math.hpp`, `memory_utils.hpp`, `metaprogramming_utils.hpp`, and `
187
187
### On Windows*
188
188
189
189
1. Change to the sample directory.
190
-
2. Configure the build system for the Agilex™ device family, which is the default.
190
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -165,7 +165,7 @@ Additionaly, the cmake build system can be configured using the following parame
165
165
### On Linux*
166
166
167
167
1. Change to the sample directory.
168
-
2. Configure the build system for the Agilex™ device family, which is the default.
168
+
2. Configure the build system for the Agilex® device family, which is the default.
169
169
170
170
```
171
171
mkdir build
@@ -209,7 +209,7 @@ Additionaly, the cmake build system can be configured using the following parame
209
209
### On Windows*
210
210
211
211
1. Change to the sample directory.
212
-
2. Configure the build system for the Agilex™ device family, which is the default.
212
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -153,7 +153,7 @@ This design measures the FPGA performance to determine how many assets can be pr
153
153
### On Linux*
154
154
155
155
1. Change to the sample directory.
156
-
2. Configure the build system for the Agilex™ device family, which is the default.
156
+
2. Configure the build system for the Agilex® device family, which is the default.
157
157
158
158
```
159
159
mkdir build
@@ -193,7 +193,7 @@ This design measures the FPGA performance to determine how many assets can be pr
193
193
### On Windows*
194
194
195
195
1. Change to the sample directory.
196
-
2. Configure the build system for the Agilex™ device family, which is the default.
196
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -146,7 +146,7 @@ Query 12 showcases the `MergeJoin` database operator. The block diagram of the d
146
146
147
147
### On Linux*
148
148
1. Change to the sample directory.
149
-
2. Configure the build system for the default target (the Agilex™ device family).
149
+
2. Configure the build system for the default target (the Agilex® device family).
150
150
```
151
151
mkdir build
152
152
cd build
@@ -195,7 +195,7 @@ Query 12 showcases the `MergeJoin` database operator. The block diagram of the d
195
195
### On Windows*
196
196
197
197
1. Change to the sample directory.
198
-
2. Configure the build system for the default target (the Agilex™ device family).
198
+
2. Configure the build system for the default target (the Agilex® device family).
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -304,7 +304,7 @@ For `constexpr_math.hpp`, `memory_utils.hpp`, `metaprogramming_utils.hpp`, `tupl
304
304
### On Linux*
305
305
306
306
1. Change to the sample directory.
307
-
2. Configure the build system for the Agilex™ device family, which is the default.
307
+
2. Configure the build system for the Agilex® device family, which is the default.
308
308
309
309
```
310
310
mkdir build
@@ -354,7 +354,7 @@ For `constexpr_math.hpp`, `memory_utils.hpp`, `metaprogramming_utils.hpp`, `tupl
354
354
### On Windows*
355
355
356
356
1. Change to the sample directory.
357
-
2. Configure the build system for the Agilex™ device family, which is the default.
357
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -57,7 +57,7 @@ You can also find more information about [troubleshooting build errors](/DirectP
57
57
58
58
The GZIP DEFLATE algorithm uses a GZIP-compatible Limpel-Ziv 77 (LZ77) algorithm for data de-duplication and a GZIP-compatible Static Huffman algorithm for bit reduction. The implementation includes three FPGA accelerated tasks (LZ77, Static Huffman, and CRC).
59
59
60
-
The FPGA implementation of the algorithm enables either one or two independent GZIP compute engines to operate in parallel on the FPGA. The available FPGA resources constrain the number of engines. By default, the design is parameterized to create a single engine when the design is compiled to target an Intel® Arria® 10 FPGA. Two engines are created when compiling for Intel® Stratix® 10 or Agilex™ FPGAs, which are a larger device.
60
+
The FPGA implementation of the algorithm enables either one or two independent GZIP compute engines to operate in parallel on the FPGA. The available FPGA resources constrain the number of engines. By default, the design is parameterized to create a single engine when the design is compiled to target an Intel® Arria® 10 FPGA. Two engines are created when compiling for Intel® Stratix® 10 or Agilex® FPGAs, which are a larger device.
61
61
62
62
This reference design contains two variants: "High Bandwidth" and "Low-Latency."
63
63
@@ -142,7 +142,7 @@ Performance results are based on testing as of October 27, 2020.
142
142
### On Linux*
143
143
144
144
1. Change to the sample directory.
145
-
2. Configure the build system for the Agilex™ device family, which is the default.
145
+
2. Configure the build system for the Agilex® device family, which is the default.
146
146
147
147
```
148
148
mkdir build
@@ -189,7 +189,7 @@ Performance results are based on testing as of October 27, 2020.
189
189
### On Windows*
190
190
191
191
1. Change to the sample directory.
192
-
2. Configure the build system for the Agilex™ device family, which is the default.
192
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -118,7 +118,7 @@ For `constexpr_math.hpp`, `pipe_utils.hpp`, and `unrolled_loop.hpp` see the READ
118
118
### On Linux*
119
119
120
120
1. Change to the sample directory.
121
-
2. Configure the build system for the Agilex™ device family, which is the default.
121
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -121,7 +121,7 @@ The `DataProducer` kernel replaces the input IO pipe in the first image. The spl
121
121
### On Linux*
122
122
123
123
1. Change to the sample directory.
124
-
2. Configure the build system for the Agilex™ device family, which is the default.
124
+
2. Configure the build system for the Agilex® device family, which is the default.
125
125
126
126
```
127
127
mkdir build
@@ -165,7 +165,7 @@ The `DataProducer` kernel replaces the input IO pipe in the first image. The spl
165
165
### On Windows*
166
166
167
167
1. Change to the sample directory.
168
-
2. Configure the build system for the Agilex™ device family, which is the default.
168
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -76,7 +76,7 @@ The QR decomposition algorithm factors a complex _m_ × _n_ matrix, where _m_
76
76
77
77
With this optimization, our FPGA implementation requires 4*m* DSPs to compute the complex floating point dot product or 2*m* DSPs for the real case. The matrix size is constrained by the total FPGA DSP resources available.
78
78
79
-
By default, the design is parameterized to process 128 × 128 matrices when compiled targeting an Intel® Arria® 10 FPGA. It is parameterized to process 256 × 256 matrices when compiled targeting a Intel® Stratix® 10 or Intel® Agilex™ FPGA; however, the design can process matrices from 4 x 4 to 512 x 512.
79
+
By default, the design is parameterized to process 128 × 128 matrices when compiled targeting an Intel® Arria® 10 FPGA. It is parameterized to process 256 × 256 matrices when compiled targeting a Intel® Stratix® 10 or Intel® Agilex® FPGA; however, the design can process matrices from 4 x 4 to 512 x 512.
80
80
81
81
To optimize the performance-critical loop in its algorithm, the design leverages concepts discussed in the following FPGA tutorials:
82
82
@@ -133,7 +133,7 @@ Additionaly, the cmake build system can be configured using the following parame
133
133
### On Linux*
134
134
135
135
1. Change to the sample directory.
136
-
2. Configure the build system for the Agilex™ device family, which is the default.
136
+
2. Configure the build system for the Agilex® device family, which is the default.
137
137
138
138
```
139
139
mkdir build
@@ -177,7 +177,7 @@ Additionaly, the cmake build system can be configured using the following parame
177
177
### On Windows*
178
178
179
179
1. Change to the sample directory.
180
-
2. Configure the build system for the Agilex™ device family, which is the default.
180
+
2. Configure the build system for the Agilex® device family, which is the default.
> **Note**: Even though the Intel DPC++/C++ OneAPI compiler is enough to compile for emulation, generating reports and generating RTL, there are extra software requirements for the simulation flow and FPGA compiles.
@@ -123,7 +123,7 @@ Additionaly, the cmake build system can be configured using the following parame
123
123
### On Linux*
124
124
125
125
1. Change to the sample directory.
126
-
2. Configure the build system for the Agilex™ device family, which is the default.
126
+
2. Configure the build system for the Agilex® device family, which is the default.
127
127
128
128
```
129
129
mkdir build
@@ -166,7 +166,7 @@ Additionaly, the cmake build system can be configured using the following parame
166
166
### On Windows*
167
167
168
168
1. Change to the sample directory.
169
-
2. Configure the build system for the Agilex™ device family, which is the default.
169
+
2. Configure the build system for the Agilex® device family, which is the default.
0 commit comments