This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Autoconfiguration question


> But the version of memcpy called from ISR context may well 
> need to be different from the memcpy in user space context: 
> different context, different rules.

In this case, user and supervisor code is linked into a single (ELF) executable,
so having different versions of these routines is not straightforward.

Anyhow, to wrap this up, it turns out the e500 ABI allows routines to use
the extended SPE registers (which is kind of obvious with hindsight).  Thus,
memcpy() is correct as written.  In this OS, ISRs are also compiled
against this ABI, thus, the ISR entry/exit routines will have to save/restore
the extended registers, even though this increases interrupt latency.

Thanks for your help!

Konrad


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