From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Whack FUNCTION_EPILOGUE_SIZE
Date: Fri, 01 Aug 2008 07:13:00 -0000 [thread overview]
Message-ID: <ud4ktnr6w.fsf@gnu.org> (raw)
In-Reply-To: <4892636D.2050007@codesourcery.com>
> Date: Thu, 31 Jul 2008 18:14:21 -0700
> From: Stan Shebs <stan@codesourcery.com>
>
> 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.
OK
prev parent reply other threads:[~2008-08-01 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 1:14 Stan Shebs
2008-08-01 7:13 ` Eli Zaretskii [this message]
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=ud4ktnr6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/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