On 30.07.2025 23:47, Dmytro Prokopchuk1 wrote: > --- a/docs/misra/deviations.rst > +++ b/docs/misra/deviations.rst > @@ -342,6 +342,12 @@ Deviations related to MISRA C:2012 Rules: > semantics that do not lead to unexpected behaviour. > - Tagged as `safe` for ECLAIR. > > + * - R11.1 > + - The conversion from 'void noreturn (*)(void *)' to 'void (*)(void *)' > + is safe because the semantics of the 'noreturn' attribute do not alter > + the calling convention or behavior of the resulting code. > + - Tagged as `safe` for ECLAIR.
As before, imo such a deviation should be generic, i.e. here independent of what parameters a function takes. If that can't be easily expressed to Eclair, then that wants stating as a justification for the deviations.ecl change to not fully cover the deviation we put in place. Having the textual deviation generic means later possible needs can be easily addressed by just a deviations.ecl change, without any adjustment to the deviations themselves. Jan
