Lines Matching full:end

7 …"PublicDescription": "Number of times the front-end is resteered when it finds a branch instructio…
69 …ed instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of the …
110         "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle",
117 … an interval where the front-end delivered no uops for a period of at least 1 cycle which was not …
122 …ter an interval where the front-end delivered no uops for a period of 128 cycles which was not int…
129 …ter an interval where the front-end delivered no uops for a period of 128 cycles which was not int…
134 …fter an interval where the front-end delivered no uops for a period of 16 cycles which was not int…
141 …ons that are delivered to the back-end after a front-end stall of at least 16 cycles. During this …
146         "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles",
153 … an interval where the front-end delivered no uops for a period of at least 2 cycles which was not…
158 …ter an interval where the front-end delivered no uops for a period of 256 cycles which was not int…
165 …ter an interval where the front-end delivered no uops for a period of 256 cycles which was not int…
170 … an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not…
177 …on": "Counts retired instructions that are delivered to the back-end after the front-end had at le…
182 …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…
201 …fter an interval where the front-end delivered no uops for a period of 4 cycles which was not inte…
206 …ter an interval where the front-end delivered no uops for a period of 512 cycles which was not int…
213 …ter an interval where the front-end delivered no uops for a period of 512 cycles which was not int…
218 …fter an interval where the front-end delivered no uops for a period of 64 cycles which was not int…
225 …fter an interval where the front-end delivered no uops for a period of 64 cycles which was not int…
230 …fter an interval where the front-end delivered no uops for a period of 8 cycles which was not inte…
237 …ons that are delivered to the back-end after a front-end stall of at least 8 cycles. During this p…
416 …hen no operation was delivered to the back-end pipeline due to instruction fetch limitations when …
420 …hen no operation was delivered to the back-end pipeline due to instruction fetch limitations when …
430 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
435 …n": "Cycles when optimal number of uops was delivered to the back-end when the back-end is not sta…
441 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
450 …to by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
460 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…
465 …n": "Cycles when optimal number of uops was delivered to the back-end when the back-end is not sta…
471 …ed by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no back-en…