From: Gunther Nikl <gni@gecko.de>
To: Ian Lance Taylor <ian@airs.com>
Cc: gcc@gcc.gnu.org
Subject: Re: inserting instructions into prologue/epilogue
Date: Thu, 04 Aug 2005 12:02:00 -0000 [thread overview]
Message-ID: <20050804120255.GA57309@lorien.int.gecko.de> (raw)
In-Reply-To: <m3slxqhpvm.fsf@gossamer.airs.com>
On Wed, Aug 03, 2005 at 10:49:49AM -0700, Ian Lance Taylor wrote:
> Gunther Nikl <gni@gecko.de> writes:
>
> > "Attempt to delete prologue/epilogue insn"
> >
> > unless the stackslot was marked with MEM_VOLATILE_P. I don't think thats
> > the proper fix.
>
> As Nathan said, you can add a USE. Or in some cases the correct fix
> is to define EPILOGUE_USES and/or EH_USES.
Is EPILOGUE_USES only for the save and restore? I would have to add
some big chunk of code to it and that would propagate to several
places. It seems emitting a USE has lower impact.
> In some cases this error message can indicate a bug in the
> prologue/epilogue code.
Here is what I am trying to do: I have a rs6000 port using V.4 ABI.
The ABI has two fixed registers: r2 (_SDA2_BASE_) and r13 (_SDA_BASE_).
I suppose normally these are initialized in an assembly file. I want
the compiler emitting the appropriate load through a function attribute.
Since I change the register it has to be saved and restored as well.
Gunther
next prev parent reply other threads:[~2005-08-04 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 14:40 Gunther Nikl
2005-08-03 14:50 ` Nathan Sidwell
2005-08-03 14:53 ` Nathan Sidwell
2005-08-03 15:27 ` Gunther Nikl
2005-08-03 18:09 ` Richard Henderson
2005-08-03 17:50 ` Ian Lance Taylor
2005-08-04 12:02 ` Gunther Nikl [this message]
2005-08-04 16:57 ` Ian Lance Taylor
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=20050804120255.GA57309@lorien.int.gecko.de \
--to=gni@gecko.de \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
/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).