:function:::int:check_mf_cycles:hilo_history *history, signed64 time, const char *new
{
+ /* There are no timing requirements in vr5500 code. */
+ if (MIPS_MACH (SD) == bfd_mach_mips5500)
+ return 1;
if (history->mf.timestamp + 3 > time)
{
sim_engine_abort (SD, CPU, CIA, "HILO: %s: %s at 0x%08lx too close to MF at 0x%08lx\n",
Just this,We have had very bad experiences with trying to make a single function
serve two different ABI's in the past. (mips_push_arguments seems to
have been cleaned up since I last looked; it was a real mess.) So
while using things like 'REGISTER_SIZE' and
'S390_STACK_PARAMETER_ALIGNMENT' are clearly a good idea, for the sake
of the other stuff I'd like to see a separate 's390x_push_arguments'
function written that does things right for the s390x's ABI. The
helper functions like `is_simple_arg' should be duplicated, rather
than testing GDB_TARGET_IS_ESAME.
Gives the thrust of the rationale. Namely, its better to, from the
start, have separate independant functions and not confuse things by
adding more and more if(ISA/ABI) specific gunk. As JimB noted, the MIPS
is the not so shining example of how to do things (i.e., how things can
go wrong).