> 
> I think returning 0 here is a better idea.  If the function that
> you're returning from has made any (non-nullary) calls, r3 will have
> been overwritten.  Even if it doesn't make any calls, r3 is still fair
> game for the compiler to use as a temporary.
> 
> I'd like to see a comment pointing out the fact that gdb knows about
> and is able to print struct return values in inferior function calls
> due to the fact that gdb is the caller (and therefore knows the address
> of the struct return buffer).


Done.  Two comments and a bug report.
I checked in the attached.

Andrew