From: Paul Brook <paul@codesourcery.com>
To: gcc-patches@gcc.gnu.org, Bernd Schmidt <bernds@codesourcery.com>
Subject: Fix C6x 24-bit unwinding opcodes
Date: Mon, 03 Oct 2011 15:52:00 -0000 [thread overview]
Message-ID: <201110031652.04721.paul@codesourcery.com> (raw)
The C6XABI defined persoality routines ID 3 and 4 use a single 24-bit block
word of unwinding data. Patch below makes sure this is preserved, rather than
treating it as a set of unwinding opcode bytes.
I seem to have lost this bit of code when I merged the ARM and c6x
implementations.
Applied to svn trunk.
Paul
2011-10-03 Paul Brook <paul@codesourcery.com>
libgcc/
* unwind-arm-common.inc: Handle ID3/4 unwinding data.
Index: libgcc/unwind-arm-common.inc
===================================================================
--- libgcc/unwind-arm-common.inc (revision 179178)
+++ libgcc/unwind-arm-common.inc (working copy)
@@ -583,7 +583,7 @@ __gnu_unwind_pr_common (_Unwind_State st
uws.words_left = 0;
uws.bytes_left = 3;
}
- else
+ else if (id < 3)
{
uws.words_left = (uws.data >> 16) & 0xff;
uws.data <<= 16;
next reply other threads:[~2011-10-03 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 15:52 Paul Brook [this message]
2011-10-21 22:43 ` Bernd Schmidt
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=201110031652.04721.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=bernds@codesourcery.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).