SDCC currently considers \o as o (i.e. just handling it like the
standard escapes \, \?, etc). Similarly for any \X not defined by the standard.
I think there should be a warning or error for such escapes.
Their use is likely either a typo (programmer error), or an expectation of SDCC supporting some extension that it does not support (also programmer error).
Diff: