This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computer science This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science ??? This article has not yet received a rating on the project's importance scale. Things you can help WikiProject Computer science with: Here are some tasks awaiting attention: Article requests : Requested articles/Applied arts and sciences/Computer science, computing, and Internet Cleanup : Computer science articles needing attention Computer science articles needing expert attention Copyedit : Computing Expand : Computer science Infobox : Computer science articles without infoboxes Maintain : Timeline of computing 2020–present Photo : Find pictures for the biographies of computer scientists (see List of computer scientists) Computing articles needing images Stubs : Computer science stubs Unreferenced : WikiProject Computer science/Unreferenced BLPs Project-related : Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Is Android's JIT compiler considered dynarec? Their new ART obviously isn't. — Preceding unsigned comment added by Kvswim (talk • contribs) 02:08, 12 December 2013 (UTC)Reply

In the second paragraph, what the heck is Corn? And second, the example really has little to with Dynamic Recompilation and is closer to High Level Emulation. Dynamic Recompilation stores blocks of recompiled code in memory, so that it doesn't have to decode and simulate instructions everytime.

lda #4
adc ($4), x

would become something like:

mov eax, 4
push eax
push eax
call getX86Addess
mov ebx, eax
pop eax
add ebx, edx
adc eax, [ebx]

and decoding will continue until a branch/jump/call is reached. 24.13.122.71 01:52, 19 June 2006 (UTC)Reply

http://corn.telefonia.pl/ apparently, I've never heard of it either. Feel free to insert a better example, I'm by no means an expert on the subject. StealthFox 11:32, 19 June 2006 (UTC)Reply

I have suggested that Dynarec be merged into this article, as they are two articles on the same thing. Anyone see any reason why not? StealthFox 02:16, 26 December 2005 (UTC)Reply

"In an ironic twist in real world usage, the first sequence of instructions (RISC) is generally preferred over the next (CISC). The reasons provided are slow CISC processor execution, prevention of pipeline stalls, and lower hardware overheads."

Preferred where? Code compiled for i386 is chock-full of rep.cmps . Given the platform's performance and market share, surely i386 is representative of the real world?

I don't really get the example. It doesn't explain, why dynamic recompilation is needed. There is absolutely nothing in this example that cannot be recompiled in a static way. --- Krstfrs (talk) 13:37, 10 March 2009 (UTC)Reply

This is true I may write a better/revised one Bostwickenator (talk) 06:21, 15 April 2012 (UTC)Reply

Should the article be merged with Just-in-time compilation? Both appear to be describing the same thing. Smk65536 (talk) 06:35, 16 May 2014 (UTC)Reply

Hello there! Well, JIT should be considered as a form of dynamic recompilation, so it would be better to keep these articles separate. Dynamic recompilation is a much broader term as it includes other approaches used in emulators and virtual machines, for example it covers various cross-platform emulations. — Dsimic (talk | contribs) 15:13, 18 May 2014 (UTC)Reply

Heartily agreed --Bostwickenator (talk) 04:34, 20 May 2014 (UTC)Reply