[ColdFire 34/63] Don't emit a nop after noreturn calls
Richard Sandiford
richard@codesourcery.com
Wed Jan 10 11:44:00 GMT 2007
m68k_output_function_epilogue has code to output a NOP after a noreturn
call. It's there so that gdb can tell that the call came from the
current function, not the one after it. However, Dan says that gdb
doesn't need such help now, so this patch removes it.
Richard
gcc/
200x-xx-xx Kazu Hirata <kazu@codesourcery.com>
* config/m68k/m68k.c (m68k_output_function_epilogue): Don't
output a NOP for empty epilogues.
Index: gcc/config/m68k/m68k.c
===================================================================
--- gcc/config/m68k/m68k.c 2007-01-09 15:02:13.000000000 +0000
+++ gcc/config/m68k/m68k.c 2007-01-09 15:02:13.000000000 +0000
@@ -1079,12 +1079,7 @@ m68k_output_function_epilogue (FILE *str
if (GET_CODE (insn) == NOTE)
insn = prev_nonnote_insn (insn);
if (insn && GET_CODE (insn) == BARRIER)
- {
- /* Output just a no-op so that debuggers don't get confused
- about which function the pc is in at this address. */
- fprintf (stream, "\tnop\n");
- return;
- }
+ return;
#ifdef FUNCTION_EXTRA_EPILOGUE
FUNCTION_EXTRA_EPILOGUE (stream, size);
More information about the Gcc-patches
mailing list