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.
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.
The DMA interrupt handlers for multiple drivers took two parameters
but the signature expected by the registration function assumed the
handlers had three parameters. The solution was to conditionally add
a third parameter (ignored) and mark it with RTEMS_UNUSED.
For the UART and USART drivers, there was a type defined for the
handler which included the incorrect signature. Changed to use the
DMA handler type.
Implements the required bsp directives for the 'new' style rtems
interrupt system. Previously, uC5282 only supported interrupts through
the BSP_installVME_isr directive.
BSP_installVME_isr still behaves the same, but is instead implemented
using the new IRQ directives. To ensure compatibility with existing
EPICS related code without causing subtle bugs, BSP_installVME_isr will
also poke at the EPORT interrupt settings to enable IRQ1 when installing
a "fake VME" interrupt (vector >= 192).
This also fixes a regression from e9cb088995 that broke clock interrupt
handlers, leading to the BSP crashing shortly after boot.
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>
Silences -Werror=unused-parameter warnings in psximfs and psximfs04
tests by explicitly casting the unused argument to void. This fixes
the build on strict compilers.
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.
Added API header OK test in psxtests/psxhdrs
as a part of my work to GSoC 25
note that functions ppoll(), sem_clockwait() and timespec_get()
don't have a prototype yet so the tests will fail. I won't
add them to the libpsxhdrs.yml file until my PR is approved in newlib.
The ZYNQMP_RPU_CORE_INDEX macro is undefined in the code, making
BSP_ARM_GIC_MULTI_PROCESSOR_SECONDARY never being defined, which makes
the secondary core initialize GIC again. It should be changed to
ZYNQMP_RPU_SPLIT_INDEX.
Add build options for start address, vector base, and BRAM length,
wire them into the microblaze_fpga linker script and BSP group,
and add the dependencies to the kcu105_qemu BSP spec.
This change was made to address GCC -Wtype-limits warnings.
In this case, the counter variable was uint16_t but the value
of ALTERA_EPCQ_CONTROLLER2_1US_TIMEOUT_VALUE was too large
for uint16_t.
