www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/01/26/11:30:23

From: George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: asm code
Date: 26 Jan 1998 16:04:35 GMT
Organization: Oxford University, England
Message-ID: <6aic6j$nmi$2@news.ox.ac.uk>
References: <34cb0769 DOT 598790 AT nntpserver DOT swip DOT net> <OhTziCmK9GA DOT 185 AT upnetnews03>
NNTP-Posting-Host: sable.ox.ac.uk
Lines: 20
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Mon, 26 Jan 1998 08:46:35 -0500 in comp.os.msdos.djgpp DeHackEd
<Not DOT given AT out> wrote:

: I think what you should do is pushl your registers onto the stack first, and 
: your last command should popl them back. I am a newbee on the topic of asm, but 
: I do know some of the basics, such as the stack. This way you don't have to put 
: in ANY variables on the clobbered list, even though they get changed.

But the whole point of the clobber list is so that you don't need to
do this.  If gcc isn't using a register, for example, the normal
push/pop system would save it anyway; with the clobber list, gcc gets
to decide whether or not it matters if the value of a register is
clobbered.  Using gcc-allocated registers as well also allows it to
reuse a value stored in another register.  Extended assembler is A
Good Thing. :)

-- 
Regards,

george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019