RTEMS | Remove set_vector() across all architectures and BSPs (#5215)

[Joel Sherrill (@joel)]

Joel Sherrill created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5215



## Summary
Issue https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/4171 is specific to the SPARC architecture but includes a detailed description of the solution. This solution needs to be applied to every use of _set_vector()_ and then the various implementations removed. In rtems itself, this reports 60 references to be evaluated and updated:

```
rtems]$ grep -rl set_vector cpukit/ bsps testsuites/ | wc -l
60
```

These references are spread across at least 6 architectures and some common code.

There may also be references in other repositories and at least a grep must be done to ensure that no code or documentation references this function any longer.

Where possible, BSP test results should be posted.

As a minimum, successful runs of _rtems-bsp-builder_ using gcc 14 or later must be posted. This is because GCC 14 is pickier about many warnings and its new errors are what bumped the priority of deleting use of _set_vector()_. 

### Project Details
If this is used as a student project, then the pool of possible mentors includes all core developers. @joel, @gedare, @opticron, or @chris are likely to be the primary mentor with assistance as needed based on the BSP or architecture. 

### Pre-set options

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5215
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/20250214/7b7d192a/attachment-0001.htm>