Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.compilers > #1174

Re: Self-modifying code, Function pointers & { Safety, Security}

Show all headers | View raw

> [The major reasons for self-modifying code historically were for
> address modification for indexing and subroutine returns.  Index
> registers and indirect addressing provide instruction modification as
> the instruction is executed, making those modifications go away.  For
> runtime code generation, there have been a variety of approaches to
> controlled addition of code to running programs, which I could dig up
> if people care. -John]

I was planning to discontinue self-modifying code entirely.
For runtime code generation, I was planning to bank entirely
upon runtime hooks(mapping instructions of an interpreter to
API hooks).

I will proceed on these two premises if only others advised.

Sincerely,
Seima Rao.

Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Self-modifying code, Function pointers & { Safety, Security} Seima Rao <seimarao@gmail.com> - 2014-03-07 21:34 +0530
  Re: Self-modifying code, Function pointers & { Safety, Security} Kaz Kylheku <kaz@kylheku.com> - 2014-03-09 20:36 +0000
    Re: Self-modifying code, Function pointers & { Safety, Security} Terrence Enger <tenger@iseries-guru.com> - 2014-03-15 09:29 -0400
  Re: Self-modifying code, Function pointers & { Safety, Security} Martin Ward <martin@gkc.org.uk> - 2014-03-14 14:15 +0000
  Re: Self-modifying code, Function pointers & { Safety, Security} seimarao@gmail.com - 2014-03-20 00:42 -0700
    Re: Self-modifying code, Function pointers & { Safety, Security} federation2005@netzero.com - 2014-04-13 12:41 -0700
      Re: Self-modifying code, Function pointers & { Safety, Security} Stefan Monnier <monnier@iro.umontreal.ca> - 2014-04-16 09:18 -0400

csiph-web