aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp/gxxint.texi
diff options
context:
space:
mode:
authorMike Stump <mrs@gcc.gnu.org>1994-11-29 00:59:16 +0000
committerMike Stump <mrs@gcc.gnu.org>1994-11-29 00:59:16 +0000
commitdb5ae43ff2ce49f1cbe66a0e16f4e079b702580b (patch)
tree572fd369f71d068ba440682b16fe5848cd15d1cf /gcc/cp/gxxint.texi
parentc7a7ac465ec752e3c21494ff810e95e851f36ac3 (diff)
downloadgcc-db5ae43ff2ce49f1cbe66a0e16f4e079b702580b.zip
gcc-db5ae43ff2ce49f1cbe66a0e16f4e079b702580b.tar.gz
gcc-db5ae43ff2ce49f1cbe66a0e16f4e079b702580b.tar.bz2
49th Cygnus<->FSF merge
From-SVN: r8570
Diffstat (limited to 'gcc/cp/gxxint.texi')
-rw-r--r--gcc/cp/gxxint.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/cp/gxxint.texi b/gcc/cp/gxxint.texi
index 2441da1..fc9157c 100644
--- a/gcc/cp/gxxint.texi
+++ b/gcc/cp/gxxint.texi
@@ -1185,7 +1185,7 @@ On an rs6000, xlC stores exception objects on that stack, under the try
block. When is unwinds down into a handler, the frame pointer is
adjusted back to the normal value for the frame in which the handler
resides, and the stack pointer is left unchanged from the time at which
-the object was throwed. This is so that there is always someplace for
+the object was thrown. This is so that there is always someplace for
the exception object, and nothing can overwrite it, once we start
throwing. The only bad part, is that the stack remains large.