> Another perfectly good solution is for the compiler to assure that the return > PC is always in the > right scope to begin with. All it takes is to include a (never executed) NOP > following any non-returning > CALL at the last address of the routine.Such calls are not common, plus many > environments align > the beginning of (any subsequent) functions anyway so padding bytes are > likely to be available. As a > result, such "extra" bytes are not going to be a space issue.
In fact, the PA-RISC and Itanium calling conventions specifically require this. -cary _______________________________________________ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
