From: Stan Shebs <stan@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Whack FUNCTION_EPILOGUE_SIZE
Date: Fri, 01 Aug 2008 01:14:00 -0000 [thread overview]
Message-ID: <4892636D.2050007@codesourcery.com> (raw)
The last configuration that needed the FUNCTION_EPILOGUE_SIZE hack
(umax) went away years ago, no reason to keep the code around any longer.
Stan
2008-07-31 Stan Shebs <stan@codesourcery.com>
* coffread.c (coff_symtab_read): Remove FUNCTION_EPILOGUE_SIZE.
* gdbint.texinfo: Remove FUNCTION_EPILOGUE_SIZE.
Index: coffread.c
===================================================================
RCS file: /cvs/src/src/gdb/coffread.c,v
retrieving revision 1.82
diff -u -p -r1.82 coffread.c
--- coffread.c 27 May 2008 19:29:51 -0000 1.82
+++ coffread.c 1 Aug 2008 00:25:53 -0000
@@ -1026,22 +1026,9 @@ coff_symtab_read (long symtab_offset, un
finish_block (new->name, &local_symbols, new->old_blocks,
new->start_addr,
-#if defined (FUNCTION_EPILOGUE_SIZE)
- /* This macro should be defined only on
- machines where the
- fcn_aux_saved.x_sym.x_misc.x_fsize
- field is always zero.
- So use the .bf record information that
- points to the epilogue and add the size
- of the epilogue. */
- cs->c_value
- + FUNCTION_EPILOGUE_SIZE
- + ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT
(objfile)),
-#else
fcn_cs_saved.c_value
+ fcn_aux_saved.x_sym.x_misc.x_fsize
+ ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT
(objfile)),
-#endif
objfile
);
within_function = 0;
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.286
diff -u -p -r1.286 gdbint.texinfo
--- doc/gdbint.texinfo 29 Jul 2008 20:26:53 -0000 1.286
+++ doc/gdbint.texinfo 1 Aug 2008 00:25:53 -0000
@@ -3657,13 +3657,6 @@ return gdbarch_addr_bits_remove (gdbarch
@noindent
@xref{TARGET_READ_SP}, which this method replaces.
-@item FUNCTION_EPILOGUE_SIZE
-@findex FUNCTION_EPILOGUE_SIZE
-For some COFF targets, the @code{x_sym.x_misc.x_fsize} field of the
-function end symbol is 0. For such targets, you must define
-@code{FUNCTION_EPILOGUE_SIZE} to expand into the standard size of a
-function's epilogue.
-
@item GCC_COMPILED_FLAG_SYMBOL
@itemx GCC2_COMPILED_FLAG_SYMBOL
@findex GCC2_COMPILED_FLAG_SYMBOL
next reply other threads:[~2008-08-01 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 1:14 Stan Shebs [this message]
2008-08-01 7:13 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4892636D.2050007@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox