diff mbox

[m32c] document named address space option.

Message ID 201010222157.o9MLvQb4016916@greed.delorie.com
State New
Headers show

Commit Message

DJ Delorie Oct. 22, 2010, 9:57 p.m. UTC 
Here's the corresponding doc changes...  Ok to apply?

	* doc/extend.texi (Named Address Spaces): Document the M32C named
	address space.

Comments

Michael Meissner Oct. 22, 2010, 10:03 p.m. UTC | #1 
On Fri, Oct 22, 2010 at 05:57:26PM -0400, DJ Delorie wrote:
> 
> Here's the corresponding doc changes...  Ok to apply?

Ok.  I would imagine a port maintainer shouldn't need to get a GR/doc approval
to update the documentation for a port.
DJ Delorie Oct. 22, 2010, 10:27 p.m. UTC | #2 
> Ok.  I would imagine a port maintainer shouldn't need to get a
> GR/doc approval to update the documentation for a port.

Usually I don't, but in this case we're still starting out and we
don't have the obvious list-of-targets in that part of the
documentation.  I thought perhaps the doc folks might want it
restructured to be more list-like now that SPU wasn't the only one.

Anyway, applied.  Thanks!
diff mbox

Patch

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