| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Flexible array members must not appear in the middle of a structure.
|
| |
|
| |
|
|
|
|
|
|
| |
Bug was introduced by 78baeb757957fa0807c30e6c4d21ae99c9639e6a.
Update #3199.
|
|
|
|
| |
Allow assert checks in test begin actions and setup fixture methods.
|
|
|
|
|
| |
This name better reflects the execution envirnoment in which the cache
is fully loaded with valid data unrelated to the body request handler.
|
|
|
|
|
|
|
| |
This primitive test case memory allocator uses memory from the low-level
memory information provided by the BSP. At the beginning of each test
case, the memory available to the test case is reinitialized. This
allows the use of a simple allocate only allocator.
|
| |
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
|
|
|
|
| |
Normally, the expected test step must be a compile time constant. Allow
variable expected test steps for the T_step() and T_assert_step(). This
can be used for parameterized test loops with individual fixtures.
Remove the ability to use custom failure messages due to some
implementation constraints.
Update #3199.
|
|
|
|
|
|
| |
Support a new test plan for each nested fixture.
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
| |
Return the produced character count. There is no need for a NUL
termination.
Update #3199.
|
|
|
|
|
|
|
|
| |
Add support to record thread switch events. This can be used to check
that a blocking operation results in the expected sequence of thread
switches.
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
| |
This macro magic is in line with C11 and C++11, but limits the maximum
count of arguments.
Update #3199.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename internal function T_check_true() to T_check() and use the new
flag T_CHECK_FMT to indicate if a format string is present. This is a
preparation step to make the format string optional.
Make the check context the first parameter.
The API remains the same.
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
|
| |
Rename this header file to later move <t.h> to <rtems/test.h>. The main
feature provided by <rtems/test-info.h> is the output of standard test
information which is consumed by the RTEMS Tester.
Update #3199.
|
|
|
|
|
|
|
| |
Update #3706.
RTEMS Application Loader, RTEMS Runtime Link Editor, Status Checks
and Test Support
|
| |
|
|
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.
|