From: Nick Garnett <nickg@ecoscentric.com>
To: kevin_lemay@agilent.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] i386 Memory Size Problem
Date: Tue, 25 Nov 2003 17:29:00 -0000 [thread overview]
Message-ID: <m37k1ol5kk.fsf@miso.calivar.com> (raw)
In-Reply-To: <1BEBA5E8600DD4119A50009027AF54A010FAE480@axcs04.cos.agilent.com>
kevin_lemay@agilent.com writes:
> Nick,
>
> I found some sample code that makes the calls that I need.
>
> Are there any examples of storing to the c/C++ variables that would
> help me to do the port?
Writing to C++ variables is slightly hard since you need to handle the
name mangling. So it's best to always use C variables from assembler.
A straighforward movl will do the trick.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-25 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 16:30 kevin_lemay
2003-11-25 17:29 ` Nick Garnett [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 20:13 kevin_lemay
2003-12-03 10:29 ` Nick Garnett
2003-11-25 22:24 kevin_lemay
2003-11-26 11:45 ` Nick Garnett
2003-11-24 22:53 kevin_lemay
2003-11-25 10:57 ` Nick Garnett
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=m37k1ol5kk.fsf@miso.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=kevin_lemay@agilent.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).