Changeset d389819 in rtems-docs for porting/task_context.rst


Ignore:
Timestamp:
Jan 18, 2016, 5:37:40 AM (4 years ago)
Author:
Amar Takhar <amar@…>
Branches:
4.11, 5, master
Children:
f916fca
Parents:
11e1a6f
git-author:
Amar Takhar <amar@…> (01/18/16 05:37:40)
git-committer:
Amar Takhar <verm@…> (05/03/16 00:51:24)
Message:

Convert all Unicode to ASCII(128)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • porting/task_context.rst

    r11e1a6f rd389819  
    201201registers assumed to be preserved across subroutine calls
    202202must be preserved.  These registers may be saved in
    203 the task’s context area or on its stack.  However, the
     203the task's context area or on its stack.  However, the
    204204stack pointer and address to resume executing the task
    205205at must be included in the context (normally the subroutine
    206206return address to the caller of ``_Thread_Dispatch``.
    207 The decision of where to store the task’s context is based
     207The decision of where to store the task's context is based
    208208on numerous factors including the capabilities of
    209209the CPU architecture itself and simplicity as well
    210210as external considerations such as debuggers wishing
    211 to examine a task’s context.  In this case, it is
     211to examine a task's context.  In this case, it is
    212212often simpler to save all data in the context area.
    213213
     
    293293indicates whether or not this CPU model has FP support.  For example, the
    294294definition of the i386ex and i386sx CPU models would set I386_HAS_FPU to
    295 FALSE to indicate that these CPU models are i386’s without an i387 and
     295FALSE to indicate that these CPU models are i386's without an i387 and
    296296wish to leave floating point support out of RTEMS when built for the
    297297i386_nofp processor model.  On a CPU with a built-in FPU like the i486,
     
    400400format is not critical for the implementation of the floating point
    401401context switch routines.  In this case, there is no need to figure out the
    402 exact format – only the size.  Of course, although this is enough
     402exact format - only the size.  Of course, although this is enough
    403403information for RTEMS, it is probably not enough for a debugger such as
    404404gdb.  But that is another problem.
     
    417417The CPU_CONTEXT_FP_SIZE macro is set to the size of the floating point
    418418context area. On some CPUs this will not be a "sizeof" because the format
    419 of the floating point area is not defined – only the size is.  This is
     419of the floating point area is not defined - only the size is.  This is
    420420usually on CPUs with a "floating point save context" instruction.  In
    421421general, though it is easier to define the structure as a "sizeof"
Note: See TracChangeset for help on using the changeset viewer.