From mint-bounce@lists.fishpool.fi Sat Aug 27 22:54:05 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] what's wrong with this code? From: Odd Skancke To: MiNT List In-Reply-To: <4300E409.3080101@klockars.net> References: <20050810084953.GA29857@hysteria.sk> <1123778764.5688.9.camel@linuxbox> <20050815064515.GA21766@hysteria.sk> <4300696F.9000301@klockars.net> <1124121226.5688.19.camel@linuxbox> <4300E409.3080101@klockars.net> Content-Type: text/plain Date: Sat, 27 Aug 2005 22:48:40 +0000 Message-Id: <1125182920.5860.4.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.9 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: man, 15,.08.2005 kl. 20.50 +0200, skrev Johan Klockars: > Uhm... > In what universe does a 680x0 RTE pull any stack pointer what-so-ever > from the stack? > > On the stack you'll only find (for a Trap on a 680x0, x > 0): > 0(a7).w - SR > 2(a7).l - return address > 6(a7).w - vector offset (not there on the 68000) > > No stack pointer is ever saved before entering an exception handler, nor > restored on RTE. > There are physically separate registers for the various stack pointers, > which just get "remapped" in hardware depending on the bits in SR. You're right.