Joel Sherrill commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5300#note_126673 Yes. This sounds like something that should be reported upstream. When you get a link to an issue or discussion upstream, post that in this issue. This issue then can be updated as things move upstream. Hopefully they have a fix. In the meantime, we could disable this line of code with a _#ifndef __rtems___ wrapper. That would let the march to warning free code continue without this being a blocker. Disabling the line would NOT close this issue. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5300#note_126673 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
