Sebastian Huber commented on a discussion on bsps/mips/shared/irq/vectorexceptions.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1401#note_158529 > { > - (void) frame; > - > uint32_t cause; > uint32_t exc; > > mips_get_cause( cause ); > exc = (cause >> 2) & 0x1f; > > + if ( exc == MIPS_EXCEPTION_RI && mips_emulate_rdhwr_ulr( frame ) ) { > + return; > + } > + > mips_exception_frame = frame; > bsp_interrupt_handler_dispatch( exc ); > mips_exception_frame = NULL; What do you mean with "hacky"? Is it the `mips_exception_frame` global variable? I can change this, but it will have a larger impact on the existing APIs of the MIPS port. The fatal extensions should be used for things which are configurable or optional. TLS is a C language feature which should work out of the box. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1401#note_158529 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-02avwc8fzlr5nb0lvsspyn5np-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
