I know the field is a fast moving one, but my goodness. The target architecture is used in the world of embedded hardware where product lifetimes often can be measured in decades (think locomotives, industrial installations, ships, etc.)
For compliance and certification reasons alone you're often stuck with using older software versions. 6 years isn't actually that bad in that context. Keep in mind that many devices, such as ATMs, still use OS/2(!) or Windows 2000(!) as their operating systems, for example.
Although my meaning was more that in the context of opening an issue on a project, this version is ancient.
Far as I can tell the only thing I get out of newer versions of gcc is more pointless warnings to silence.
* have reduced source code for the example, preferably a single source file, in a form which can be compiled
* have the exact command line used to build it
* have the exact compiler version being used
* apply to a supported version of the compiler (GCC 5 is from 2015...)
* include an accurate explanation of what is wrong with the generated code
Maybe the last one is covered by this blog post, but things like
> I can maybe understand the subtraction of constant 0, if there’s another code path that jumps to 7ba6
suggests that the author hasn't fully analysed the generated code.
The analysis is OK though and with source code it would be a pretty good bug report.