This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This addresses sign comparison warnings in the RFS.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This addresses sign comparison warnings in the tftp file system.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This addresses sign comparison warnings in the dosfs.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This moves the JFFS2 sources imported from Linux into the contrib/
subdirectory since that is where 3rd party sources belong. The import
revision is currently "v6.1" with some alterations.
This warning indicates the potential for using a local variable which
is not guaranteed to be preserved across a setjmp()/longjmp() pair.
In this case, it was a false positive and the warning was disabled.
Updates #5364.
This adds a missing text description for an internal error and updates
the spinternalerror02 test to check for the correct end of internal
error definitions.
Also includes a related libio change.
Most of these warnings were between int or ssize_t and size_t.
In particular, various POSIX system calls like read() and write()
return ssize_t and comparing that value with the sizeof a buffer
is a common source of these warnings. Another common source is
using an int as the iterator in a for loop with the limit being
a size_t.
With the type change, some printf() specifiers needed to change also.
Many files with Eric Valette as author only had his email address.
This led to them being missed in previous relicensing passes.
This effort relicensed where possible and made efforts to have the
file follow the RTEMS standard for top of files (SPDX, Doxygen,
and then copyright/license).
Updates #5418.
The call to Untar_FromMemory_Print() on line 400 was passing
false as the third argument. "rtems_printer *" was expected.
In C previous to C23, false was a macro defined as 0 and could
be converted to a pointer. In C23, false, true, and bool are keywords.
Fixes -Wsign-compare compile warnings in CAN code. This introduces
the change in rtems_ctucanfd_initialize where ntxbufs is changed from
int to unsigned int, thus making the ntxbufs < 0 obsolete.
Signed-off-by: Michal Lenc <michallenc@seznam.cz>
Previously, the function returned true when node->next == NULL, but did
not verify that node->previous was also NULL.
The updated implementation checks the node->next == NULL and in
RTEMS_DEBUG it checks node->previous == NULL before reporting the
node is off-chain.
These changes ensure that the off-chain invariant is verified in
the RTEMS_DEBUG
This change Updates RTEMS issue #4812.
This change eliminates an unnecessary blank paragraph in
cpukit/include/rtems/score/copyrt.h. RTEMS documentation requires single
spaced paragraphs, and the previous formatting contained consecutive
blank lines.
The modification is formatting-only and has no functional impact.
Updates #4807.
This patch removes a superfluous blank paragraph from
cpukit/include/rtems/rtems/barrierdata.h. The formatting issue created
two consecutive blank lines inside the documentation block, which is not
permitted by RTEMS style rules.
This update improves documentation consistency without altering runtime
behavior.
Updates #4807.
Signed-off-by: Asif Khan <asif21012006@gmail.com>
This patch removes an unnecessary blank paragraph in
cpukit/include/rtems/confdefs/iodrivers.h to comply with RTEMS
documentation formatting guidelines. Only one blank line should separate
paragraphs, and this change enforces that rule.
Updates #4807.
These changes were made to address GCC -Wtype-limits warnings.
In this case, the variables were unsigned and there was no need to
check them for being <= 0.
Updates #5388.
- Extend IMFS and libio headers to define default allocator/deallocator ops
and logic for configuring memfile_ops.
- Update imfs_memfile to use custom allocators for memory blocks.
- Fix imfs_statvfs.f_bfree calculation to respect user-defined ops.
- Add psximfs03 test case to validate custom allocator behavior.
- Refactor psximfs01 to share helper functions with psximfs03.
Added the implementation of timespec_get() with tests.
The implementation used clock_gettime() as a reference.
The tests used psxtimes01 as a reference.
Updates
rtems/programs/gsoc#69
The sizeof(ino_t) can potentially vary based on the target. This
resulted in -Wformat warnings. Add PRIdino_t in <rtems/inttypes.h>
to have a portable format specifier.
Closes#5393.
This adds summary support to the build with a global option to enable
this support and necessary changes to the imported summary support
source to integrate it into the build system and resolve errors.
Move JFFS2 from the Cygwin implementation of CRC32 to the zlib
implementation which can take advantage of hardware acceleration and
reduces code duplication. Synthetic benchmarks on AArch64 hardware show
approximately a 17x improvement in CRC32 calculation speed and
real-world testing with JFFS2 shows a 1% improvement in mount times, a
5% improvement in data write times, and a 9% improvement in garbage
collection times.
A test was written to compare hash generation between the two algorithms
and a partition was created with one and then remounted with the other
with no errors.
rtems_message_queue_broadcast() may, under certain circumstances, copy
the message to tasks which were not waiting on the message queue when
the broadcast started, and may copy the message multiple times to the
same task.
This behaviour is, based on discussion in #4804, something that might
not change in the short term, so expose it in the user documentation.
The wording is copied with modifications from an existing internal
requirements note.
Also correct "none-atomic" -> "non-atomic" in said internal requirements
note.
The changes were auto-generated from rtems-central.
Uses the CONFIGURE_MAXIMUM_PRIORITY to set the priority range for
EDF and CBS schedulers under the control of applications.
The default priority behavior is now the same as other schedulers.
The user API to get a task's current priority returns 0 for deadline
driven tasks.
Fixes#5390
When a callback does not exist, the Flashdev API should return error
where possible instead of success. When the API returns success for
missing callbacks, the Flashdev API client code may end up using
uninitialized variables as if they were filled by the API.
Closes#5391
