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: How is _GLOBAL_REENT meant to be used?


> -----Original Message-----
> From: newlib-owner@sourceware.org 
> Ok, but what if you do not use newlib for threads within a 
> process (f.e. under linux), but as independent tasks in a 
> RTOS, then you want to keep the information about open files 
> separate for each task.

You don't want to do this in modern systems :-).

The approach of emulating e.g., Unix processes as RTOS ``tasks'' dates
to before the time that Unix supported threads.  With the advent of
pthreads, it is much better to map RTOS ``tasks'' to Pthread
``threads''.  E.g., this mapping acknowledges the fact that all memory
is shared.

> I think same applies to atexit lists. 
> ECOS could have the same problem probably.


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