Lionel Debroux (./11) :
I assume "build it" is a multiple step process, for testing multiple compilation option sets ? If not, the way you're describing is too simple-minded to catch calling convention mismatches (and possibly other errors, too)

If you test a header whose prototypes are autogenerated by the HSF tools, the calling convention will necessarily be independent of the -mregparm switch used, our tool automatically adds an attribute for that. Your prototypes were wrong no matter what -mregparm switch was used on the command line, as __ATTR_LIB_C__ sets a fixed number of register parameters, overriding the switch on the command line.

You spend lots of time trolling and finding excuses for not doing your maintainership work, so you do have time.

I'd need both a lot more time and a lot more concentration to do that work than to discuss things on message boards. Usually, when I frequent the forums, it's when I'm too tired to do anything else.