From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Cupertino Miranda <Cupertino.Miranda@synopsys.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: RE: [ARC] Fix stack unwinding for ARC
Date: Fri, 03 Nov 2017 10:55:00 -0000 [thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE89667B671F@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <EB86EB452ADE4B44B294F7149B8A277702711AD9@DE02WEMBXB.internal.synopsys.com>
> - Fix to unwinding. Now is is possible to unwind from syscall
> wrappers, signals and functions with dynamic stack allocation.
>
> - Patch also fixes millicode. Although millicode save and restore functions
> would change blink, the calls to those functions were not clobbering blink.
>
Approved and committed with minor modifications.
Cheers,
Claudiu
prev parent reply other threads:[~2017-11-03 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 13:44 Cupertino Miranda
2017-11-03 10:55 ` Claudiu Zissulescu [this message]
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=098ECE41A0A6114BB2A07F1EC238DE89667B671F@de02wembxa.internal.synopsys.com \
--to=claudiu.zissulescu@synopsys.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=andrew.burgess@embecosm.com \
--cc=gcc-patches@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).