Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: GDB Administrator <gdbadmin@sourceware.org>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Thu Oct 13 01:55:36 UTC 2011
Date: Thu, 13 Oct 2011 13:54:00 -0000	[thread overview]
Message-ID: <20111013135412.GA2276@host1.jankratochvil.net> (raw)
In-Reply-To: <20111013015536.GA23787@sourceware.org>

On Thu, 13 Oct 2011 03:55:36 +0200, GDB Administrator wrote:
> 216a217
> > gdb/dwarf2-frame-tailcall.c:283: obsolete: get_frame_base: Replace get_frame_base with get_frame_id, get_frame_base_address, get_frame_locals_address, or get_frame_args_address.
> gdb/dwarf2-frame-tailcall.c:283:	addr = get_frame_base (this_frame) - cache->entry_cfa_sp_offset;

This comes from my:
	[patch 04/12] entryval#3: Virtual tail call frames
	http://sourceware.org/ml/gdb-patches/2011-09/msg00556.html

where the code is specific to gdbarch_sp_regnum, so I think it should operate
with this_frame->stack_addr, which is exactly what get_frame_base does.

I understand such code ($sp simulation with shift for return address in tail
call frames) could have been rather gdbarch-specific but I am not aware of any
gdbarch where it should be done differently.  If such gdbarch exists and there
is interest in fixing this very minor feature of the entryval patchset this
can be moved to gdbarch-specific code where maybe get_frame_base may not be
appropriate.  I have no idea without being aware of any such gdbarch.


Regards,
Jan


  reply	other threads:[~2011-10-13 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  1:55 GDB Administrator
2011-10-13 13:54 ` Jan Kratochvil [this message]
2011-10-13 15:00   ` Ulrich Weigand
2011-10-13 21:15     ` entryval tail call frames $sp adjustment vs. gdbarches [Re: New ARI warning Thu Oct 13 01:55:36 UTC 2011] Jan Kratochvil
2011-10-19 16:05       ` Ulrich Weigand
2011-10-21  0:34         ` Jan Kratochvil
2011-10-21  0:45         ` Jan Kratochvil

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=20111013135412.GA2276@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdbadmin@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