What are the uses of self modifying code?

Turns out that the Wikipedia entry on "self-modifying code" has a great list:

1. Semi-automatic optimization of a state dependent loop.
2. Runtime code generation, or specialization of an algorithm in runtime or loadtime (which is popular, for example, in the domain of real-time graphics) such as a general sort utility preparing code to perform the key comparison described in a specific invocation.
3. Altering of inlined state of an object, or simulating the high-level construction of closures.
4. Patching of subroutine address calling, as done usually at load time of dynamic libraries, or, on each invocation patching the subroutine's internal references to its parameters so as to use their actual addresses. Whether this is regarded as 'self-modifying code' or not is a case of terminology.
5. Evolutionary computing systems such as genetic programming.
6. Hiding of code to prevent reverse engineering, as through use of a disassembler or debugger.
7. Hiding of code to evade detection by virus/spyware scanning software and the like.
8. Filling 100% of memory (in some architectures) with a rolling pattern of repeating opcodes, to erase all programs and data, or to burn-in hardware.
9. Compression of code to be decompressed and executed at runtime, e.g., when memory or disk space is limited.
10. Some very limited instruction sets leave no option but to use self-modifying code to achieve certain functionality. For example, a "One Instruction Set Computer" machine that uses only the subtract-and-branch-if-negative "instruction" cannot do an indirect copy (something like the equivalent of "*a = **b" in the C programming language) without using self-modifying code.
11. Altering instructions for fault-tolerance

On the point about thwarting hackers using self-modifying code:

Over the course of several firmware updates, DirectTV slowly assembled a program on their smart card to destroy cards that have been hacked to illegally receive unpaid channels. See Jeff's Coding Horror article on the Black Sunday Hack for more information.

I've seen self-modifying code used for:

1. speed optimisation, by having the program write more code for itself on the fly

2. obsfucation, to make reverse engineering much harder

In former times where RAM was limited, self modifying code was used to save memory. Nowadays for example application compression utilities like UPX are used to decompress/modify the own code after loading a compressed image of the application.

Because the Commodore 64 doesn't have many registers and has a 1Mhz processor. When you need to read a memory address offset by a value it is easier to modify the source.

@Reader:
LDA $C000
STA $D020
INC Reader+1
JMP Reader

That's the last time I wrote self-modifying code anyway :-)

Artificial Intelligence?

Because it's really really cool, and sometimes that's reason enough.

Lots of reasons. Off the top of my head:

• Runtime class construction and meta programming. For example, having a class factory that takes a connection to an SQL table and generates a client class specialized for that table (with accessors for the columns, find methods, etc.).

• Then of course there's the famous bitblt example, and the regexp analogs.

• Dynamically optimizing based on RT information a la tracing JITs

• Subtype specialization of ada style generic functions in an accretive environment.

-- MarkusQ

Dynamic linking is a kind of self-modification (patching absolute and/or relative jump locations) ... that's normally done by the O/S's program loader, though.

Neural networks are kind of self-modifying code.

Then there are evolutionary algorithms which modify themselves.

Mike Abrash described the Pixomatic code generator for Dr. Dobb's Journal a while back: http://www.ddj.com/architect/184405807 . That's a software 3d dx7(?) compatible rasterizer.

LOL - i've written self-modifying code on two occasions:

1. when first learning assembly language, before i understood indirect indexed access
2. accidentally, as pointer bugs in assembly language and C

i can imagine that there may be scenarios where self-modifying code would be more efficient than alternatives, but nothing obvious leaps to mind. In general, this is something to avoid - debugging nightmare, etc. - unless you are deliberately trying to obfuscate as mentioned above.

Applications which implement their own scripting languages often do this. For example, database servers often compile stored procedures (or queries) this way.

Dynamic code generation in SwiftShader is a form of self modifying code that enables it to efficiently implement Direct3D 9 on the CPU.

Modern example: I have a script that needs JWT token to work. To request a token interactive login is needed or use a refresh token that is issued with new JWT token. Would be nice to store refresh token in the script and update it each time it is being executed