Lines Matching full:blocks
118 basic blocks (BBs, straight-line sequences of code) into
162 basic blocks for C++ compiled with optimisation on. Generating
216 block is placed on the freed blocks queue
220 Keeping <computeroutput>free</computeroutput>'d blocks in this
222 to them. However, once the volume of blocks in the free queue
224 blocks are finally removed from the queue.</para>
257 Valgrind to run just some number of basic blocks, and then run
341 every 1000 basic blocks, which means 500 to 2000 times/second
351 This does a complete check of all blocks and chains in an
378 <para>The JITter parses x86 basic blocks into sequences
570 <para>Valgrind translates client (original) basic blocks into
571 instrumented basic blocks, which live in the translation cache
770 the in-memory state is up-to-date between basic blocks. (This
773 blocks).</para>
901 transformation passes, all on straight-line blocks of UCode (type
923 <computeroutput>N</computeroutput> basic blocks. It also re-JITs
1733 basic blocks, and not at arbitrary points inside basic
1734 blocks. And the consequence of that is that we can only
1735 deliver signals to the client in between basic blocks. None
1752 rather unexciting, and shown below. On longer basic blocks they
2007 undramatic because it is so short; longer blocks benefit more
2175 transformations on straight-line blocks of code.</para>
2238 <para>Every 1000 basic blocks, we see if more signals have
