This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] update gcc-3.4/changes web page with Xtensa ABI changes
- From: Bob Wilson <bwilson at tensilica dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 05 Mar 2004 15:27:18 -0800
- Subject: [PATCH] update gcc-3.4/changes web page with Xtensa ABI changes
- Organization: Tensilica, Inc.
Here is a patch to the gcc-3.4/changes web page to describe my recent ABI
changes for the Xtensa port. I ran it through the HTML validator and it looks OK.
OK to commit?
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.4/changes.html,v
retrieving revision 1.102
diff -u -r1.102 changes.html
--- changes.html 25 Feb 2004 10:08:49 -0000 1.102
+++ changes.html 5 Mar 2004 23:22:14 -0000
@@ -786,6 +786,26 @@
<h3>Xtensa</h3>
<ul>
+ <li>Several ABI bugs have been fixed:
+ <ul>
+ <li>For big-endian processors, the padding of aggregate return values
+ larger than a word has changed. If the size of an aggregate return
+ value is not a multiple of 32 bits, previous versions of GCC inserted
+ padding in the most-significant bytes of the first return value
+ register. Aggregates larger than a word are now padded in the
+ least-significant bytes of the last return value register used.
+ Aggregates smaller than a word are still padded in the most-significant
+ bytes. The return value padding has not changed for little-endian
+ processors.</li>
+ <li>Function arguments with 16-byte alignment are now properly
+ aligned.</li>
+ <li>The implementation of the <code>va_list</code> type has changed.
+ A <code>va_list</code> value created by <code>va_start</code> from a
+ previous release cannot be used with <code>va_arg</code> from this
+ release, or vice versa.</li>
+ </ul>
+ Unfortunately, these changes break binary compatibility with earlier
+ releases.</li>
<li>More processor configuration options for Xtensa processors are
supported:
<ul>