This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[m32c] document named address space option.
- From: DJ Delorie <dj at redhat dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 22 Oct 2010 17:57:26 -0400
- Subject: [m32c] document named address space option.
Here's the corresponding doc changes... Ok to apply?
* doc/extend.texi (Named Address Spaces): Document the M32C named
address space.
Index: doc/extend.texi
===================================================================
--- doc/extend.texi (revision 165861)
+++ doc/extend.texi (working copy)
@@ -1217,13 +1217,13 @@ Fixed-point types are supported by the D
@cindex named address spaces
As an extension, the GNU C compiler supports named address spaces as
defined in the N1275 draft of ISO/IEC DTR 18037. Support for named
address spaces in GCC will evolve as the draft technical report changes.
Calling conventions for any target might also change. At present, only
-the SPU target supports other address spaces. On the SPU target, for
+the SPU and M32C targets support other address spaces. On the SPU target, for
example, variables may be declared as belonging to another address space
by qualifying the type with the @code{__ea} address space identifier:
@smallexample
extern int __ea i;
@end smallexample
@@ -1234,12 +1234,17 @@ support, or generate special machine ins
space.
The @code{__ea} identifier may be used exactly like any other C type
qualifier (e.g., @code{const} or @code{volatile}). See the N1275
document for more details.
+On the M32C target, with the R8C and M16C cpu variants, variables
+qualified with @code{__far} are accessed using 32-bit addresses in
+order to access memory beyond the first 64k bytes. If @code{__far} is
+used with the M32CM or M32C cpu variants, it has no effect.
+
@node Zero Length
@section Arrays of Length Zero
@cindex arrays of length zero
@cindex zero-length arrays
@cindex length-zero arrays
@cindex flexible array members