From: "H.J. Lu" <hongjiu.lu@intel.com>
To: gcc-patches@gcc.gnu.org
Cc: Jason Merrill <jason@redhat.com>
Subject: [PATCH] PR debug/81570: dwarf2cfi.c: Update cfa.offset in create_pseudo_cfg
Date: Thu, 27 Jul 2017 19:50:00 -0000 [thread overview]
Message-ID: <20170727195014.GA10240@gmail.com> (raw)
execute_dwarf2_frame is called for each funtion. But create_cie_data
is called only once to initialize cie_cfi_row for all functions. Since
INCOMING_FRAME_SP_OFFSET may be different for each function, we can't
use the same INCOMING_FRAME_SP_OFFSET in cie_cfi_row for all functions.
This patch sets cie_cfi_row->cfa.offset to INCOMING_FRAME_SP_OFFSET in
create_pseudo_cfg which is called for each function.
Tested on x86-64. OK for trunk?
Thanks.
H.J.
PR debug/81570
* dwarf2cfi.c (create_pseudo_cfg): Set cie_cfi_row->cfa.offset
to INCOMING_FRAME_SP_OFFSET.
---
gcc/dwarf2cfi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/dwarf2cfi.c b/gcc/dwarf2cfi.c
index a5f9832fc4a..c40f31d2f20 100644
--- a/gcc/dwarf2cfi.c
+++ b/gcc/dwarf2cfi.c
@@ -2831,6 +2831,9 @@ create_pseudo_cfg (void)
memset (&ti, 0, sizeof (ti));
ti.head = get_insns ();
ti.beg_row = cie_cfi_row;
+ /* Set cfa.offset to INCOMING_FRAME_SP_OFFSET here since it may be
+ different for each function. */
+ cie_cfi_row->cfa.offset = INCOMING_FRAME_SP_OFFSET;
ti.cfa_store = cie_cfi_row->cfa;
ti.cfa_temp.reg = INVALID_REGNUM;
trace_info.quick_push (ti);
--
2.13.3
next reply other threads:[~2017-07-27 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 19:50 H.J. Lu [this message]
2017-10-25 4:02 ` Jason Merrill
2017-10-31 18:00 ` H.J. Lu
2017-11-02 14:51 ` Jason Merrill
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=20170727195014.GA10240@gmail.com \
--to=hongjiu.lu@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jason@redhat.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).