This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
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.
JFFS2 uses the high values of the unsigned flash offset in a raw node
reference as special identifiers and specifies them using negative
integer literals. This disables those errors for non-RTEMS source and
constrains such comparisons in RTEMS code to avoid larger reworks of the
JFFS2 upstream source.
Previously, if a user defined a stack checker reporter but disabled
the stack checker (e.g. for testing), the build would fail with an #error.
This change removes the error to allow flexible configuration.
Closes#5425
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 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 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 primarily in the CBS.
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 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
