This is the mail archive of the gcc-help@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: Issue with debugging information generated by compiler gcc 4.3.3.

From: Ian Lance Taylor <iant at google dot com>
To: sumanth <sumanth dot gundapneni at redpinesignals dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Sat, 04 Apr 2009 09:45:02 -0700
Subject: Re: Issue with debugging information generated by compiler gcc 4.3.3.
References: <49D5D552.6000904@redpinesignals.com> <m3prft7ppr.fsf@google.com> <49D6DE32.1060002@redpinesignals.com>

sumanth <sumanth.gundapneni@redpinesignals.com> writes:

> I compiled the code with -O0 optimization level
> Ours is a customized processor which I am not supposed to reveal its
> name/ arch

If this is a private port of gcc, then there is very little that we can
do to help.  All the details of where variables are placed in the stack
frame are handled by the target code.  If you are not getting the
results that you want, then that is the place to look, probably in
INITIAL_ELIMINATION_OFFSET and/or the "prologue" insn expansion.

Ian

References:
- Issue with debugging information generated by compiler gcc 4.3.3.
  - From: sumanth
- Re: Issue with debugging information generated by compiler gcc 4.3.3.
  - From: Ian Lance Taylor
- Re: Issue with debugging information generated by compiler gcc 4.3.3.
  - From: sumanth

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