RTEMS | ts-validation-intr assumes UINT32_MAX is an invalid interrupt priority (#5578)

[Gedare Bloom (@gedare)]

Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5578

Assignee: Gedare Bloom

## Summary
<!--
Please provide as much information as possible such as error messages or attaching logs
-->

The validation test `ts-validation-intr.exe` is incorrect as a result, where it assumes it can use UINT32_MAX as an invalid priority. However, we don't have specified minimum or maximum interrupt priorities, they are BSP specific. The test assumes (in multiple places) that UINT_MAX is not a valid interrupt vector, but with riscv you can use anything from [0, UINT_MAX] as a vector. So you can't pass an invalid vector number through our API, because our API uses a uint32_t, so there's no possible way to test for an invalid vector number.


<!-- Pre-set options
- milestone
-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5578
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260516/05a22e75/attachment.htm>