From: Jonathan Larmour <jlarmour@redhat.com>
To: Chris Morrow <cmorrow@YottaYotta.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] hal_copy_data and hal_zero_bss
Date: Mon, 26 Feb 2001 15:22:00 -0000 [thread overview]
Message-ID: <3A9AE517.255581C4@redhat.com> (raw)
In-Reply-To: <3A99B9B6.444A2F22@YottaYotta.com>
Chris Morrow wrote:
>
> An assembler version of hal_zero_bss is included
> at the end of this message. I placed mine in
> vectors.S. I'm not sure where you would like it.
That's fine. Thanks! It'll be in the next anon CVS update.
> Currently the start up code calls hal_copy_data before
> hal_zero_bss. Since at this point the stack is in bss
> when calling hal_zero_bss, I can understand why hal_zero_bss
> needs to avoid memset(). If the order of calls to mem_copy_data
> and hal_zero_bss were switched, what would prevent the use
> of memcpy in hal_copy_data? I can't think of any initialized
> data memcpy would depend on.
We don't support it yet, but in future we may have profiling hooks for
debug builds for example, or very detailed tracing/instrumentation. So for
now I'd rather not introduce such a dependency.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-02-26 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 12:26 [ECOS] Header files in platform port Paul Pham
2001-01-15 13:22 ` [ECOS] hal_copy_data and hal_zero_bss Chris Morrow
2001-01-15 18:30 ` Jonathan Larmour
2001-02-25 18:05 ` Chris Morrow
2001-02-25 18:15 ` [ECOS] mips mmu setup Chris Morrow
2001-02-26 12:39 ` Jonathan Larmour
2001-02-26 15:22 ` Jonathan Larmour [this message]
2001-02-27 1:54 ` [ECOS] hal_copy_data and hal_zero_bss Chris Morrow
2001-02-27 10:25 ` Jonathan Larmour
2001-01-15 18:44 ` [ECOS] Header files in platform port Jonathan Larmour
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=3A9AE517.255581C4@redhat.com \
--to=jlarmour@redhat.com \
--cc=cmorrow@YottaYotta.com \
--cc=ecos-discuss@sourceware.cygnus.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).