This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 2/6] always define SETUP_FRAME_ADDRESSES
- From: Trevor Saunders <tbsaunde at tbsaunde dot org>
- To: Bernd Schmidt <bschmidt at redhat dot com>
- Cc: tbsaunde+gcc at tbsaunde dot org, gcc-patches at gcc dot gnu dot org
- Date: Wed, 14 Oct 2015 22:13:54 -0400
- Subject: Re: [PATCH 2/6] always define SETUP_FRAME_ADDRESSES
- Authentication-results: sourceware.org; auth=none
- References: <1444523150-15236-1-git-send-email-tbsaunde+gcc at tbsaunde dot org> <1444523150-15236-3-git-send-email-tbsaunde+gcc at tbsaunde dot org> <561B891C dot 2000603 at redhat dot com>
On Mon, Oct 12, 2015 at 12:19:08PM +0200, Bernd Schmidt wrote:
> On 10/11/2015 02:25 AM, tbsaunde+gcc@tbsaunde.org wrote:
> >From: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
> >
> >gcc/ChangeLog:
> >
> >2015-10-10 Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
> >
> > * defaults.h (SETUP_FRAME_ADDRESSES): New default definition.
> > * builtins.c (expand_builtin_return_addr): Adjust.
> > * doc/tm.texi: Likewise.
> > * doc/tm.texi.in: Likewise.
> > * except.c (expand_builtin_unwind_init): Likewise.
>
> If we go to the trouble of changing this, could we convert macros to target
> hooks instead while we're there? REVERSE_CONDITION, SETUP_FRAME_ADDRESSES
> and FRAME_ADDR_RTX all seem to be used only in a handful of ports, and
> INITIAL_FRAME_ADDRESS_RTX only in one.
I'm definitely planning to do that, but I think this is still somewhat
useful even if only to have one list to look at for what hooks need to
be added.
Trev
>
>
> Bernd