aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorKazu Hirata <kazu@cs.umass.edu>2003-10-22 18:22:09 +0000
committerKazu Hirata <kazu@gcc.gnu.org>2003-10-22 18:22:09 +0000
commitdbacaa98b66b5651310e2dde4ed7c9e1d4115937 (patch)
treea0b51383cf135d55693adc1a8cb493304117f4a4 /gcc
parented2f11fa59957d0892749bb8243325929aa50302 (diff)
downloadgcc-dbacaa98b66b5651310e2dde4ed7c9e1d4115937.zip
gcc-dbacaa98b66b5651310e2dde4ed7c9e1d4115937.tar.gz
gcc-dbacaa98b66b5651310e2dde4ed7c9e1d4115937.tar.bz2
* doc/extend.texi: Mention H8S wherever H8/300H is mentioned.
From-SVN: r72813
Diffstat (limited to 'gcc')
-rw-r--r--gcc/ChangeLog4
-rw-r--r--gcc/doc/extend.texi16
2 files changed, 12 insertions, 8 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index adc1bc0..4c189a9 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2003-10-22 Kazu Hirata <kazu@cs.umass.edu>
+
+ * doc/extend.texi: Mention H8S wherever H8/300H is mentioned.
+
2003-10-22 Ulrich Weigand <uweigand@de.ibm.com>
* config/s390/s390.md ("movstr_short_64", "movstr_short_31"): Merge ...
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 1d2274f..8ebcc410 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2477,11 +2477,11 @@ instruction directly.
@item function_vector
@cindex calling functions through the function vector on the H8/300 processors
-Use this attribute on the H8/300 and H8/300H to indicate that the specified
+Use this attribute on the H8/300, H8/300H, and H8S to indicate that the specified
function should be called through the function vector. Calling a
function through the function vector will reduce code size, however;
the function vector has a limited size (maximum 128 entries on the H8/300
-and 64 entries on the H8/300H) and shares space with the interrupt vector.
+and 64 entries on the H8/300H and H8S) and shares space with the interrupt vector.
You must use GAS and GLD from GNU binutils version 2.7 or later for
this attribute to work correctly.
@@ -2493,7 +2493,7 @@ that the specified function is an interrupt handler. The compiler will
generate function entry and exit sequences suitable for use in an
interrupt handler when this attribute is present.
-Note, interrupt handlers for the H8/300, H8/300H and SH processors can
+Note, interrupt handlers for the H8/300, H8/300H, H8S, and SH processors can
be specified via the @code{interrupt_handler} attribute.
Note, on the AVR, interrupts will be enabled inside the function.
@@ -2509,7 +2509,7 @@ Permissible values for this parameter are: IRQ, FIQ, SWI, ABORT and UNDEF@.
@item interrupt_handler
@cindex interrupt handler functions on the H8/300 and SH processors
-Use this attribute on the H8/300, H8/300H and SH to indicate that the
+Use this attribute on the H8/300, H8/300H, H8S, and SH to indicate that the
specified function is an interrupt handler. The compiler will generate
function entry and exit sequences suitable for use in an interrupt
handler when this attribute is present.
@@ -2532,8 +2532,8 @@ Use this attribute on the SH for an @code{interrupt_handle} to return using
argument specifying the trap number to be used.
@item eightbit_data
-@cindex eight bit data on the H8/300 and H8/300H
-Use this attribute on the H8/300 and H8/300H to indicate that the specified
+@cindex eight bit data on the H8/300, H8/300H, and H8S
+Use this attribute on the H8/300, H8/300H, and H8S to indicate that the specified
variable should be placed into the eight bit data section.
The compiler will generate more efficient code for certain operations
on data in the eight bit data area. Note the eight bit data area is limited to
@@ -2543,8 +2543,8 @@ You must use GAS and GLD from GNU binutils version 2.7 or later for
this attribute to work correctly.
@item tiny_data
-@cindex tiny data section on the H8/300H
-Use this attribute on the H8/300H to indicate that the specified
+@cindex tiny data section on the H8/300H and H8S
+Use this attribute on the H8/300H and H8S to indicate that the specified
variable should be placed into the tiny data section.
The compiler will generate more efficient code for loads and stores
on data in the tiny data section. Note the tiny data area is limited to