#189 closed enhancement (fixed)

RTEMS User environment to use a user extension.

Reported by: Chris Johns Owned by: Joel Sherrill
Priority: lowest Milestone: 2
Component: unspecified Version: unknown
Severity: minor Keywords:
Cc: bugs@… Blocked By:
Blocking:

Description

The RTEMS user environment is currently implemented using
task variables. This requires the task variable user
extension to be active. A lib call such as chroot can
result in the task variable switch handler becoming active and
therefore changing the application's performance profile.
Libc functions should not do this.

The user environment can be implemented as a user extension.
This would be a 0 overhead solution with the PR142 patch.

Rather than a user environment, this should be implemented in terms of an rtems_reent structure defined in libcsupport as per the mail discussion. All libcsupport should be placed in this structure. Each task is given a rtems_reent and the newlib User Extension extensions slot used to hold the pointer.

Release:
cvs-head

Change History (2)

comment:1 Changed on Jul 18, 2003 at 3:16:29 PM by Joel Sherrill

Status: assignedclosed

State-Changed-From-To: open->closed
State-Changed-Why: New website has section for potential projects. This includes a

list of PRs that are wishlist items and not actively being worked
on. This PR can be reopened if someone volunteers.

comment:2 Changed on Oct 10, 2017 at 6:35:44 AM by Sebastian Huber

Component: miscunspecified
Note: See TracTickets for help on using tickets.