| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Directly use "static inline" which is available in C99 and later. This brings
the RTEMS implementation closer to standard C.
Close #3935.
|
|
|
|
| |
Updates #3053.
|
|
|
|
|
|
| |
Use common phrases for the file brief descriptions.
Update #3706.
|
|
|
|
|
|
|
|
|
| |
Rename Classic API top-level group from Classic to RTEMSImplClassic.
Use RTEMSImplClassic as a prefix for the subgroups. Change the group
names to be in line with the API group names. Use common phrases for
the group brief descriptions.
Update #3706.
|
|
|
|
| |
It is only used by rtems_partition_create().
|
|
|
|
| |
It is only used by rtems_partition_create(). Fix integer types.
|
|
|
|
|
| |
It is only used by rtems_partition_create(). Move code directly into
directive which called the inline function. Add a comment.
|
|
|
|
|
| |
It is only used by rtems_partition_create(). Move code directly into
the directive which called the inline function. Add a comment.
|
|
|
|
|
| |
It is used only by rtems_partition_return_buffer(). Make the PTCB the
first parameter. Rename to _Partition_Is_address_on_buffer_boundary().
|
|
|
|
|
| |
It is used only in one place. Make the PTCB the first parameter.
Rename it to _Partition_Is_address_a_buffer_begin().
|
|
|
|
| |
It was a trivial function call wrapper used only in one place.
|
|
|
|
| |
It was a trivial function call wrapper used only in one place.
|
|
|
|
| |
It is only used by rtems_partition_return_buffer().
|
|
|
|
| |
It is only used by rtems_partition_get_buffer().
|
| |
|
| |
|
|
|
|
|
|
| |
Use a top-level implementation group to gather implementation related
files. The use of "Impl" is shorter and matches with the *impl.h file
names.
|
|
|
|
| |
Update #3706.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Statically allocate the objects information together with the initial
set of objects either via <rtems/confdefs.h>. Provide default object
informations with zero objects via librtemscpu.a. This greatly
simplifies the workspace size estimate. RTEMS applications which do not
use the unlimited objects option are easier to debug since all objects
reside now in statically allocated objects of the right types.
Close #3621.
|
|
|
|
| |
Update #3598.
|
|
|
|
|
|
| |
Use architecture-specific integer type for an address difference.
Update #3486.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the CPU_SIZEOF_POINTER alignment instead. The internal alignment
requirement is defined by the use of Chain_Node (consisting of two
pointers) to manage the free chain of partitions.
It seems that previously the condition
CPU_PARTITION_ALIGNMENT >= sizeof(Chain_Node)
was true on all CPU ports. Now, we need an additional check.
Update #3482.
|
|
A speciality of the RTEMS build system was the make preinstall step. It
copied header files from arbitrary locations into the build tree. The
header files were included via the -Bsome/build/tree/path GCC command
line option.
This has at least seven problems:
* The make preinstall step itself needs time and disk space.
* Errors in header files show up in the build tree copy. This makes it
hard for editors to open the right file to fix the error.
* There is no clear relationship between source and build tree header
files. This makes an audit of the build process difficult.
* The visibility of all header files in the build tree makes it
difficult to enforce API barriers. For example it is discouraged to
use BSP-specifics in the cpukit.
* An introduction of a new build system is difficult.
* Include paths specified by the -B option are system headers. This
may suppress warnings.
* The parallel build had sporadic failures on some hosts.
This patch removes the make preinstall step. All installed header
files are moved to dedicated include directories in the source tree.
Let @RTEMS_CPU@ be the target architecture, e.g. arm, powerpc, sparc,
etc. Let @RTEMS_BSP_FAMILIY@ be a BSP family base directory, e.g.
erc32, imx, qoriq, etc.
The new cpukit include directories are:
* cpukit/include
* cpukit/score/cpu/@RTEMS_CPU@/include
* cpukit/libnetworking
The new BSP include directories are:
* bsps/include
* bsps/@RTEMS_CPU@/include
* bsps/@RTEMS_CPU@/@RTEMS_BSP_FAMILIY@/include
There are build tree include directories for generated files.
The include directory order favours the most general header file, e.g.
it is not possible to override general header files via the include path
order.
The "bootstrap -p" option was removed. The new "bootstrap -H" option
should be used to regenerate the "headers.am" files.
Update #3254.
|