Lines Matching full:end

7 …"PublicDescription": "Number of times the front-end is resteered when it finds a branch instructio…
70 …ed instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of the …
117         "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle",
123 … an interval where the front-end delivered no uops for a period of at least 1 cycle which was not …
128 …ter an interval where the front-end delivered no uops for a period of 128 cycles which was not int…
134 …ter an interval where the front-end delivered no uops for a period of 128 cycles which was not int…
139 …fter an interval where the front-end delivered no uops for a period of 16 cycles which was not int…
145 …ons that are delivered to the back-end after a front-end stall of at least 16 cycles. During this …
150         "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles",
156 … an interval where the front-end delivered no uops for a period of at least 2 cycles which was not…
161 …ter an interval where the front-end delivered no uops for a period of 256 cycles which was not int…
167 …ter an interval where the front-end delivered no uops for a period of 256 cycles which was not int…
172 … an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not…
178 …on": "Counts retired instructions that are delivered to the back-end after the front-end had at le…
183 …fter an interval where the front-end delivered no uops for a period of 32 cycles which was not int…
189 …ons that are delivered to the back-end after a front-end stall of at least 32 cycles. During this …
194 …fter an interval where the front-end delivered no uops for a period of 4 cycles which was not inte…
200 …fter an interval where the front-end delivered no uops for a period of 4 cycles which was not inte…
205 …ter an interval where the front-end delivered no uops for a period of 512 cycles which was not int…
211 …ter an interval where the front-end delivered no uops for a period of 512 cycles which was not int…
216 …fter an interval where the front-end delivered no uops for a period of 64 cycles which was not int…
222 …fter an interval where the front-end delivered no uops for a period of 64 cycles which was not int…
227 …fter an interval where the front-end delivered no uops for a period of 8 cycles which was not inte…
233 …ons that are delivered to the back-end after a front-end stall of at least 8 cycles. During this p…
419 …hen no operation was delivered to the back-end pipeline due to instruction fetch limitations when …
423 …hen no operation was delivered to the back-end pipeline due to instruction fetch limitations when …
433 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
438 …n": "Cycles when optimal number of uops was delivered to the back-end when the back-end is not sta…
444 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
453 …to by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
463 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
468 …n": "Cycles when optimal number of uops was delivered to the back-end when the back-end is not sta…
474 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…