| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
GCC originally needed this 20 years ago. No longer needed, so it
is being removed.
Closes #4391
|
|
|
|
|
|
| |
Improved tests for utime() and utimes() and update license.
Close #4399
|
|
|
|
| |
Close #4413.
|
|
|
|
|
| |
Added conditionals to ensure that long double function tests were only
built when newlib has long double math functions.
|
|
|
|
|
|
|
| |
Changed the way the tests were structured, added rtems_test_assert()'s,
updated psx13.scn and the license.
Update #3899
|
|
|
|
|
|
|
|
|
| |
Do not adjust the stack area begin address since this may confuse the
stack allocator and result in failed stack frees.
Account for the alignment overhead in the stack space size estimate.
Check that the stack size is in the expected interval.
|
|
|
|
| |
Signed-off-by: Eshan Dhawan <eshandhawan51@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following compiler warning:
testsuites/psxtests/psxndbm01/init.c:221:3: warning: 'strncpy' output truncated
before terminating nul copying 5 bytes from a string of the same length
221 | strncpy( test_strings, "Hello", 5 );
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition, the comments from Sebastian Huber on an old version of
such a patch have been taken into account:
1) The use of `sizeof()` in `key.dsize = sizeof( test_strings );` is wrong.
2) There is no need to allocate the string. One can simply use a string
constant.
(See https://lists.rtems.org/pipermail/devel/2020-August/061418.html)
|
|
|
|
| |
Update #4105.
|
|
|
|
|
|
|
| |
Key_ID array must have the right size, it shall have a value greater
than zero.
Note: In Standard C and C++, zero-size array is not
allowed..
|
|
|
|
|
|
| |
Since we need to test the strncpy function, using a character array with
a fixed array size in this case in place of character pointer can avoid
the string turncation warning.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
added tests for fesetexeptflag(), fegetexeptflag(),
fegetround(), fesetround().
In the test fegetround() does not return any flag
other then FE_TONEAREST in tests.
This is probably due to soft float.
The test complies successfully and returns assert
at fegetround()
Other tests run without any errors
tested on RISCV/rv32imac
The test prints nothing if runs successfully.
updates #2971
Signed-off-by: Eshan dhawan <eshandhawan51@gmail.com>
|
|
|
|
|
|
|
|
| |
Use the following variant which was already used by most source files:
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
|
|
|
|
| |
Close #3949.
|
| |
|
|
|
|
|
|
| |
This configuration option is obsolete since 2014.
Update #1367.
|
|
|
|
|
|
|
|
|
|
| |
The IO library used a POSIX key to store an optional POSIX user
environment pointer. This pulled in the POSIX keys support in every
application configuration. Add a user environment pointer to the thread
control block (TCB) instead. Applications which do not need the POSIX
user environment will just get an overhead of one pointer per thread.
Close #3882.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and
CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_*
configuration options. These two options are probably unused, see also:
* https://lists.rtems.org/pipermail/users/2019-April/033129.html
* https://lists.rtems.org/pipermail/users/2019-April/033130.html
Removing them simplifies the configuration. If there is a real user need
which shows up after the removal, we can resurrect them on demand.
Using CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE would have required the
use of the undocumented CONFIGURE_POSIX_INIT_THREAD_TABLE_NAME and
CONFIGURE_POSIX_INIT_THREAD_TABLE_SIZE configuration options.
Update #3874.
|
|
|
|
|
|
|
| |
Commit e22554535796fc29a7ed7c5e2338128e324a621d changed the error status
from ENOMEM to EAGAIN.
Update #3857.
|
|
|
|
|
|
|
|
|
| |
The FACE Technical Standard, Edition 3.0 and later require the definition
of the subcommand SOCKCLOSE in <devctl.h>.
Reference: https://www.opengroup.org/face
closes #3856.
|
|
|
|
|
|
|
| |
Rename CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS into
CONFIGURE_MAXIMUM_FILE_DESCRIPTORS.
Update #3753.
|
|
|
|
|
|
|
|
| |
Obsolete undocumented configuration options CONFIGURE_MAXIMUM_FIFOS and
CONFIGURE_MAXIMUM_PIPES. Replace these options with the new
CONFIGURE_IMFS_ENABLE_MKFIFO configuration option.
Update #3840.
|
|
|
|
| |
Use separator character '_' for all test states.
|
|
|
|
|
|
|
| |
This allows to use header includes in "config.h" to reduce the build
configuration checks.
Update #3818.
|
|
|
|
|
|
| |
The functions expect a valid string as input according to POSIX. On
systems with a NULL pointer protection the test cases ended up in
exceptions.
|
|
|
|
| |
Update #3818.
|
|
|
|
|
|
| |
Move system.h to shared init.c.
Update #3818.
|
|
|
|
| |
Update #3818.
|
| |
|
|
|
|
| |
Update #3794.
|
|
|
|
|
|
|
|
|
|
|
|
| |
+ Modify POSIX thread create extension to ensure expected
initial signal mask is provided to system threads, initial
tasks and threads, and inheritied by tasks and threads.
+ Adds psxsignal07 to verify functionality when using a POSIX
Initialization thread and POSIX threads.
+ Adds psxsignal08 to verify functionality when using a Classic API
Initialization task and Classic API tasks.
Closes #3794.
|
|
|
|
|
|
| |
Note that this test requires a functional fenv implementation. Some
targets have multilib variants where the fenv implementation is not
100% passing.
|
|
|
|
|
|
|
|
|
| |
Joel Sherrill <joel@rtems.org> modified the patch to
add autoconf logic to avoid building this new test
unless the tool chain include <ndbm.h>. The ensures
that git bisect continues to work and that the addition
of this test does not immediately force the entire
community to update their tools.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add rtems_scheduler_get_processor_maximum() as a replacement for
rtems_get_processor_count(). The rtems_get_processor_count() is a bit
orphaned. Adopt it by the Scheduler Manager. The count is also
misleading, since the processor set may have gaps and the actual count
of online processors may be less than the value returned by
rtems_get_processor_count().
Update #3732.
|
| |
|
|
|
|
|
| |
- Add a small memory test config file.
- Update the small memory PowerPC BSPs to use the new test config.
|
|
|
|
| |
Update #3334.
|
|
|
|
|
|
|
|
| |
Recursive usage of the same pthread_once_t results now in a deadlock.
Previously, an error of EINVAL was returned. This usage scenario is
invalid according to the POSIX pthread_once() specification.
Close #3334.
|
|
|
|
|
|
| |
This file is unused and makes trouble on Windows.
Updates #3638.
|
| |
|
| |
|
|
|
|
|
|
| |
Do not rely on compiler optimizations to throw away empty loops.
Close #3673.
|