This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: hal_copy_data and hal_zero_bss


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]