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 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 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 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 removes the adapters that provide glue code directly from JFFS2 to
backend storage drivers since JFFS2, the NAND driver, and the QSPI NOR
driver all support the flashdev interface.
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.
Updates #5364.
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 is to workaround a difficult bug in newlib related to
configure-time generation of this flag in newlib.h. Since there is no
multi-lib mechanism for headers, _LDBL_EQ_DBL ends up in newlib.h, which
is installed architecture wide. The default -mcpu= setting for the 68k
toolchain does support long double, so this flag is not defined in
newlib.h.
However, Coldfire targets lack support for long double, leading to some
undesirable behavior in the C/C++ standard headers. ieeefp.h has
numerous sanity checks that will #error and <cmath> from C++ will fail
to compile.
It doesn't look like this issue will ever be fixed in newlib, so we'll
just define this manually as a workaround.
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.
This changes the signature of the VMEBus DMA IRQ Callback type
(BSP_VMEDmaIRQCallback) to match that expected by BSP_installVME_isr()
when the callback is installed.
grlib has places where a function similar to memcpy() can be
provided by the driver. The signature does not match memcpy()
which led to function cast warnings when memcpy() was sufficient.
Provided a wrapper function to aligned the signatures.
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.
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.
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.
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.
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.
Most of these warnings were between int or ssize_t and size_t.
In particular, read() and write() return ssize_t and comparing
that value with the sizeof a buffer is a source of these warnings.
With the type change, some printf() specifiers needed to change also.
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.
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.
A write to the sctlr_el1 register is a 'context-changing operation'
and thus requires a pipeline flush for the change to actually take
effect on subsequent instructions.
The isb instruction gurantees this, and ensures mmu is enabled
immediately.
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).
Closes#5418.
