Re: New assembly language instructions to support OO languages?

Hans-Peter Diettrich <DrDiettrich1@aol.com>
Fri, 05 Dec 2008 06:10:43 +0100

          From comp.compilers

Related articles
New assembly language instructions to support OO languages? tony@my.net (Tony) (2008-12-04)
Re: New assembly language instructions to support OO languages? bert.hutchings@btinternet.com (bert) (2008-12-04)
Re: New assembly language instructions to support OO languages? tmk@netvision.net.il (Michael Tiomkin) (2008-12-04)
Re: New assembly language instructions to support OO languages? cg@graysage.com (Chris Gray) (2008-12-04)
Re: New assembly language instructions to support OO languages? gah@ugcs.caltech.edu (Glen Herrmannsfeldt) (2008-12-04)
Re: New assembly language instructions to support OO languages? DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-12-05)
Re: New assembly language instructions to support OO languages? DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-12-05)
Re: New assembly language instructions to support OO languages? jasen@xnet.co.nz (Jasen Betts) (2008-12-05)
Re: New assembly language instructions to support OO languages? tony@my.net (Tony) (2008-12-05)
Re: New assembly language instructions to support OO languages? tony@my.net (Tony) (2008-12-05)
Re: New assembly language instructions to support OO languages? nmm1@cam.ac.uk (2008-12-05)
Re: New assembly language instructions to support OO languages? lkrupp@pssw.com (Louis Krupp) (2008-12-05)
[29 later articles]
| List of all articles for this month |

From: Hans-Peter Diettrich <DrDiettrich1@aol.com>
Newsgroups: comp.compilers,comp.arch
Date: Fri, 05 Dec 2008 06:10:43 +0100
Organization: Compilers Central
References: 08-12-014 08-12-016 08-12-018
Keywords: OOP, architecture
Posted-Date: 05 Dec 2008 10:14:13 EST

Chris Gray schrieb:


> Well, its not a real machine, but here's an opcode description from my
> current bytecode system:
>
> bc_gmeth, /* Get METHod. The top-of-stack is the reference to an
> interface or capsule. The method vector is loaded
> from offset 16 in the interface or capsule. Then,
> the single 16 bit argument is added to the vector
> address, and the actual method reference is loaded
> from there. */
>
> I can't see it being worth adding to a real CPU, however - it would
> pipeline badly (two serialized fetches) and is trivial to build out of
> existing instructions.


ACK. Indirect addressing modes can be emulated, so that the fetches can
be interleaved by the compiler with other instructions, not requiring
memory references.


DoDi



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.