linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir Murzin" <murzin.v@gmail.com>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>,
	linux-c-programming-owner@vger.kernel.org,
	linux-c-programming@vger.kernel.org, gcc-help@gcc.gnu.org
Subject: Re: c inline assembly
Date: Sat, 18 Feb 2012 06:26:00 +0000	[thread overview]
Message-ID: <123126874-1329546468-cardhu_decombobulator_blackberry.rim.net-1355742666-@b13.c12.bise7.blackberry> (raw)

Hi!

What is you question or request? ;-)

------Original Message------
From: ratheesh kannoth
Sender: linux-c-programming-owner@vger.kernel.org
To: linux-c-programming@vger.kernel.org
To: gcc-help@gcc.gnu.org
Subject: c inline assembly
Sent: 18 Feb 2012 10:01

I am using gcc on a 32bit  intel machine.  i have defined an inline function.


This function is inline .  what all registers needs to pushed and
poped in the inline assembly so that the functions wont
disturb the registers in  the function ( in which it is C inlined  ).


inline unsigned long hello(unsigned long a)

{
 int b;
 asm ("movl %1, %%eax;
      " movl %1, %%ebx;
       "movl  %1, %%ecx;
       "movl  %1, %%esi;
       "movl  %1, %%edi;

       "movl %%eax, %0;"
       :"=r"(b)        /* output */
       :"r"(a)         /* input */
 );
}
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Best wishes,
Vladimir Murzin

             reply	other threads:[~2012-02-18  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  6:26 Vladimir Murzin [this message]
     [not found] <CAGZFCEEaJ7ZsNAmWCF-nDtsjs70U7fqEVvTXEaCt9Tmk1dcemQ@mail.gmail.com>
2012-02-18  6:01 ` c inline assembly ratheesh kannoth
2012-02-19  5:14   ` Ian Lance Taylor
2012-02-19 16:46   ` Gedare Bloom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=123126874-1329546468-cardhu_decombobulator_blackberry.rim.net-1355742666-@b13.c12.bise7.blackberry \
    --to=murzin.v@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=linux-c-programming-owner@vger.kernel.org \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=ratheesh.ksz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).