X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Thu, 25 Oct 2007 11:23:57 -0400
Message-Id: <200710251523.l9PFNv2X022561@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <ffpkhp$p9o$1@aioe.org> (do_not_have@nohavenot.cmm)
Subject: Re: Using inline asm
References: <471FEAC8 DOT 5179 DOT 2FAB88DB AT gerritvn DOT gpvno DOT co DOT za> <200710250120 DOT l9P1KEb2032374 AT envy DOT delorie DOT com> <ffp07f$66t$1 AT aioe DOT org> <200710250306 DOT l9P36dqi002391 AT envy DOT delorie DOT com> <ffpkhp$p9o$1 AT aioe DOT org>
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Thanks.  Okay, it doesn't, so correct the code...  I wasn't sure if
> the asm directive inserted a pusha; popa combination into the
> stackframe, say instead of push ebp; pop ebp, or used some other
> method.  That might mess up returns...

The intention of the asm is to tell gcc exactly what the opcode does,
including side effects.  It's up to gcc to decide if/when it needs to
preserve registers or whatnot.  That's why it's important to be
specific about what the opcode does.