From: Joern Rennecke <joern.rennecke@superh.com>
To: dk@artimi.com (Dave Korn)
Cc: joern.rennecke@superh.com ('Joern Rennecke'), gcc@gcc.gnu.org
Subject: Re: How can INITIAL_FRAME_POINTER_OFFSET be made correct?
Date: Fri, 19 Mar 2004 18:57:00 -0000 [thread overview]
Message-ID: <200403191724.i2JHOHB14108@linsvr1.uk.superh.com> (raw)
In-Reply-To: <NUTMEGB2cBzQk8PXOr5000001bb@NUTMEG.CAM.ARTIMI.COM> from "Dave Korn" at Mar 19, 2004 05:04:28
If you mention LINK_REGS in EPILOGUE_USES, you'll have to assume that
it is always 'used', and use REG_N_SETS to check if it's clobbered.
Otherwise, I'd suggest setting a watchpoint to find out where exactly
regs_ever_live[LINK_REGS] is set.
next prev parent reply other threads:[~2004-03-19 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 16:46 Dave Korn
2004-03-19 16:59 ` Joern Rennecke
2004-03-19 17:55 ` Dave Korn
2004-03-19 18:31 ` Joern Rennecke
2004-03-19 18:41 ` Dave Korn
2004-03-19 18:57 ` Joern Rennecke [this message]
2004-03-19 19:49 ` Dave Korn
2004-03-21 18:08 ` Hans-Peter Nilsson
2004-03-19 21:02 ` Richard Henderson
2004-03-22 17:31 ` Dave Korn
2004-03-22 23:09 ` Richard Henderson
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=200403191724.i2JHOHB14108@linsvr1.uk.superh.com \
--to=joern.rennecke@superh.com \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).