From: DJ Delorie <dj@redhat.com>
To: mark.kettenis@xs4all.nl
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] m32c-tdep.c: Add virtual_frame_pointer function
Date: Wed, 28 Jun 2006 21:34:00 -0000 [thread overview]
Message-ID: <200606282133.k5SLXcAM017959@greed.delorie.com> (raw)
In-Reply-To: <200606282129.k5SLTfc8004816@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Wed, 28 Jun 2006 23:29:41 +0200 (CEST))
> You probably should change legacy_virtual_frame_pointer to check for
> SP_REGNUM < NUM_REGS + NUM_PSEUDO_REGS instead.
Note that m32c has two stack pointers, and the one that's used depends
on the CPU flags. This is separate from the flag that determines
which register bank is in use.
next prev parent reply other threads:[~2006-06-28 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 13:29 Corinna Vinschen
2006-06-28 21:29 ` Mark Kettenis
2006-06-28 21:34 ` DJ Delorie [this message]
2006-06-29 2:34 ` Daniel Jacobowitz
2006-06-29 10:51 ` Corinna Vinschen
2006-06-29 13:08 ` Corinna Vinschen
2006-07-12 19:13 ` Daniel Jacobowitz
2006-07-13 12:01 ` Corinna Vinschen
2006-06-29 13:18 ` Daniel Jacobowitz
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=200606282133.k5SLXcAM017959@greed.delorie.com \
--to=dj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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