From: Bob Wilson <bwilson@tensilica.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] document Xtensa backend changes for 4.3
Date: Wed, 14 Nov 2007 09:18:00 -0000 [thread overview]
Message-ID: <473A500C.3000209@tensilica.com> (raw)
In-Reply-To: <473A27F6.2010809@tensilica.com>
[-- Attachment #1: Type: text/plain, Size: 234 bytes --]
I have updated the 4.3 release notes to mention the Xtensa backend's change from
sjlj to DWARF unwinding, and while I was at it, I included a few other less
significant changes. I checked the revised file with the HTML validator.
[-- Attachment #2: gcc-changes.patch --]
[-- Type: text/x-diff, Size: 1061 bytes --]
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/changes.html,v
retrieving revision 1.82
diff -u -r1.82 changes.html
--- changes.html 2 Nov 2007 07:27:23 -0000 1.82
+++ changes.html 14 Nov 2007 01:23:55 -0000
@@ -745,6 +745,20 @@
option and can be accessed using new built-in functions.</li>
</ul>
+<h3>Xtensa</h3>
+ <ul>
+ <li>Stack unwinding for exception handling now uses by default a
+ specialized version of DWARF unwinding. This is not
+ binary-compatible with the setjmp/longjmp (sjlj) unwinding used
+ for Xtensa with previous versions of GCC.</li>
+ <li>For Xtensa processors that include the Conditional Store option,
+ the built-in functions for atomic memory access are now implemented
+ using <code>S32C1I</code> instructions.</li>
+ <li>If the Xtensa NSA option is available, GCC will use it to implement
+ the <code>__builtin_ctz</code> and <code>__builtin_clz</code>
+ functions.</li>
+ </ul>
+
<h2>Documentation improvements</h2>
prev parent reply other threads:[~2007-11-14 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 23:44 [Xtensa] use DWARF unwinding Bob Wilson
2007-11-14 9:18 ` Bob Wilson [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=473A500C.3000209@tensilica.com \
--to=bwilson@tensilica.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).