This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Preserving the argument spills for GDB

From: Ian Lance Taylor <iant at google dot com>
To: Jean Christophe Beyler <jean dot christophe dot beyler at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 09 Nov 2009 07:40:33 -0800
Subject: Re: Preserving the argument spills for GDB
References: <c568a2600911031101n2aff21a8te6218ea41b0b2795@mail.gmail.com> <mcrbpjjqn80.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <c568a2600911040824q57a9837djfaea247691f4e883@mail.gmail.com> <mcreioensrf.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <c568a2600911090721r11a55172web6de199634b052e@mail.gmail.com>

Jean Christophe Beyler <jean.christophe.beyler@gmail.com> writes:

> How can I force the prologue to keep this instruction. It is useless
> only in the case that there is no function call or no alloca. But I
> have a case where there is a function call and it is still removed.

Make the hard frame pointer register a fixed register, or add it to
EPILOGUE_USES.

Ian

Follow-Ups:
- Re: Preserving the argument spills for GDB
  - From: Jean Christophe Beyler

References:
- Preserving the argument spills for GDB
  - From: Jean Christophe Beyler
- Re: Preserving the argument spills for GDB
  - From: Ian Lance Taylor
- Re: Preserving the argument spills for GDB
  - From: Jean Christophe Beyler
- Re: Preserving the argument spills for GDB
  - From: Ian Lance Taylor
- Re: Preserving the argument spills for GDB
  - From: Jean Christophe Beyler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]