Re: Backend for a stack-oriented architecture

2025-02-24 Thread Florian Weimer
* Michael Matz: > Hello, > > On Mon, 24 Feb 2025, Florian Weimer wrote: > >> .proc fib (_long) (_long) >> # Argument/result register: %3 >> # return address register: %2 >> # local register: %1 >> # outgoing argument/return register: %0 >> .framesize 24 # in bytes, three registers excluding the

Re: Backend for a stack-oriented architecture

2025-02-24 Thread Jeff Law via Gcc
On 2/24/25 4:32 AM, Florian Weimer wrote: As a hobby project, I'm working on a mostly memory-safe architecture that is targeted at direct software emulation. The majority of its instructions have memory operands that are relative to the stack pointer. Calls and returns adjust the stack point

Re: Backend for a stack-oriented architecture

2025-02-24 Thread Michael Matz via Gcc
Hello, On Mon, 24 Feb 2025, Florian Weimer wrote: > .proc fib (_long) (_long) > # Argument/result register: %3 > # return address register: %2 > # local register: %1 > # outgoing argument/return register: %0 > .framesize 24 # in bytes, three registers excluding the incoming argument ... > ret

Backend for a stack-oriented architecture

2025-02-24 Thread Florian Weimer
As a hobby project, I'm working on a mostly memory-safe architecture that is targeted at direct software emulation. The majority of its instructions have memory operands that are relative to the stack pointer. Calls and returns adjust the stack pointer, so I suppose one could say that the archite