From: Michael Eager <eager@eagerm.com>
To: David Holsgrove <david.holsgrove@xilinx.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Edgar Iglesias <edgari@xilinx.com>,
John Williams <jwilliams@xilinx.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>, Tom Shui <tshui@xilinx.com>
Subject: Re: [Patch, microblaze]: Enable DWARF exception handling support
Date: Tue, 19 Mar 2013 17:05:00 -0000 [thread overview]
Message-ID: <51489AD2.4050802@eagerm.com> (raw)
In-Reply-To: <f4fde0bc-9667-483e-8ca2-dcf11611c7a8@CO9EHSMHS029.ehs.local>
On 03/18/2013 05:47 AM, David Holsgrove wrote:
> Add DWARF exception handling support for MicroBlaze.
>
> Changelog
>
> 2013-03-18 Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> David Holsgrove <david.holsgrove@xilinx.com>
>
> * common/config/microblaze/microblaze-common.c: Remove
> TARGET_EXCEPT_UNWIND_INFO definition.
> * config/microblaze/microblaze-protos.h: Add microblaze_eh_return prototype.
> * gcc/config/microblaze/microblaze.c: (microblaze_must_save_register,
> microblaze_expand_epilogue, microblaze_return_addr): Handle
> calls_eh_return
> (microblaze_eh_return): New function.
> * gcc/config/microblaze/microblaze.h: Define RETURN_ADDR_OFFSET,
> EH_RETURN_DATA_REGNO, MB_EH_STACKADJ_REGNUM, EH_RETURN_STACKADJ_RTX,
> ASM_PREFERRED_EH_DATA_FORMAT
> * gcc/config/microblaze/microblaze.md: Define eh_return pattern.
Hi David --
I see about 50 more failures (an increase from 137 to 189) in the g++
regression tests after applying this patch. I haven't looked at the
failures in detail.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2013-03-19 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 12:49 David Holsgrove
2013-03-19 17:05 ` Michael Eager [this message]
2013-03-19 21:30 ` David Holsgrove
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=51489AD2.4050802@eagerm.com \
--to=eager@eagerm.com \
--cc=david.holsgrove@xilinx.com \
--cc=edgari@xilinx.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwilliams@xilinx.com \
--cc=nmekala@xilinx.com \
--cc=tshui@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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).