2008-08-07 Joel Sherrill <joel.sherrill@OARcorp.com>

* user/datatypes.t: Add rtems_name. Add comment about
	rtems_task_argument changing from simple unsigned thirty two bit
	integer to being derived from a C99 uintptr_t in 4.8 and newer.
This commit is contained in:
Joel Sherrill
2008-08-07 13:45:23 +00:00
parent 0f4856601e
commit 747c92ebad
2 changed files with 18 additions and 1 deletions

View File

@@ -1,3 +1,9 @@
2008-08-07 Joel Sherrill <joel.sherrill@OARcorp.com>
* user/datatypes.t: Add rtems_name. Add comment about
rtems_task_argument changing from simple unsigned thirty two bit
integer to being derived from a C99 uintptr_t in 4.8 and newer.
2008-08-04 Joel Sherrill <joel.sherrill@OARcorp.com>
PR 1263/doc

View File

@@ -169,6 +169,13 @@ the entry point to the send packet routine for an MPCI implementation.
@item @code{@value{DIRPREFIX}mpci_table} is the data structure
containing the configuration information for an MPCI.
@findex rtems_name
@item @code{@value{DIRPREFIX}name} is the data type used to
contain the name of a Classic API object. It is an unsigned
thirty-two bit integer which can be treated as a numeric
value or initialized using @code{@value{DIRPREFIX}build_name} to
contain four ASCII characters.
@findex rtems_option
@item @code{@value{DIRPREFIX}option} is the data type
used to specify which behavioral options the caller desires.
@@ -224,7 +231,11 @@ RTEMS Task.
@findex rtems_task_argument
@item @code{@value{DIRPREFIX}task_argument} is the data
type for the argument passed to each RTEMS task.
type for the argument passed to each RTEMS task. In RTEMS 4.7
and older, this is an unsigned thirty-two bit integer. In
RTEMS 4.8 and newer, this is based upon the C99 type @code{uintptr_t}
which is guaranteed to be an integer large enough to hold a
pointer on the target architecture.
@findex rtems_task_begin_extension
@item @code{@value{DIRPREFIX}task_begin_extension} is the