From be3798c151873f79d266510391ac99228ab15e07 Mon Sep 17 00:00:00 2001 From: Phil Edwards Date: Mon, 15 Jul 2002 20:05:54 +0000 Subject: [PATCH] index.html: Fix download links. 2002-07-15 Phil Edwards * docs/html/faq/index.html: Fix download links. * docs/html/faq/index.txt: Regenerate. * docs/html/17_intro/porting.html: Regenerate from earlier changes. From-SVN: r55462 --- libstdc++-v3/ChangeLog | 6 ++ libstdc++-v3/docs/html/17_intro/porting.html | 86 ++++++++++---------- libstdc++-v3/docs/html/faq/index.html | 6 +- libstdc++-v3/docs/html/faq/index.txt | 4 +- 4 files changed, 54 insertions(+), 48 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index c74227d794d..4e6465c6e36 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2002-07-15 Phil Edwards + + * docs/html/faq/index.html: Fix download links. + * docs/html/faq/index.txt: Regenerate. + * docs/html/17_intro/porting.html: Regenerate from earlier changes. + 2002-07-11 Rainer Orth * configure.target (target_os switch): Allow for irix6*o32 diff --git a/libstdc++-v3/docs/html/17_intro/porting.html b/libstdc++-v3/docs/html/17_intro/porting.html index 347c73f891e..e791f92dc74 100644 --- a/libstdc++-v3/docs/html/17_intro/porting.html +++ b/libstdc++-v3/docs/html/17_intro/porting.html @@ -3,15 +3,15 @@ Porting libstdc++-v3 - - + +

Porting libstdc++-v3

Node:Top, -Next:, -Up:(dir) +Next:, +Up:(dir)

Porting libstdc++-v3

@@ -37,20 +37,20 @@ library, but you should at least try some minimal test cases.

Here are the primary steps required to port the library:

Node:Operating system, -Next:, -Previous:Top, -Up:Top +Next:, +Previous:Top, +Up:Top

Operating system

@@ -76,7 +76,7 @@ standard target triplet; e.g., the solaris2.8 in sparc-sun-solaris2.8.

The first file to create in this directory, should be called -bits/os_defines.h. This file contains basic macro definitions +os_defines.h. This file contains basic macro definitions that are required to allow the C++ library to work with your C library. This file should provide macro definitions for __off_t, __off64_t, and __ssize_t. Typically, this just looks @@ -124,14 +124,14 @@ this: #endif -

We recommend copying an existing bits/os_defines.h to use as a +

We recommend copying an existing os_defines.h to use as a starting point.

Node:CPU, -Next:, -Previous:Operating system, -Up:Top +Next:, +Previous:Operating system, +Up:Top

CPU

@@ -160,9 +160,9 @@ appropriate for your chip.

Node:Character types, -Next:, -Previous:CPU, -Up:Top +Next:, +Previous:CPU, +Up:Top

Character types

@@ -170,20 +170,20 @@ Up:Top

The library requires that you provide three header files to implement character classification, analogous to that provided by the C libraries <ctype.h> header. You can model these on the files provided in -config/os/generic/bits. However, these files will almost +config/os/generic. However, these files will almost certainly need some modification. -

The first file to write is bits/ctype_base.h. This file provides +

The first file to write is ctype_base.h. This file provides some very basic information about character classification. The libstdc++-v3 library assumes that your C library implements <ctype.h> by using a table (indexed by character code) containing integers, where each of these integers is a bit-mask indicating whether the character is -upper-case, lower-case, alphabetic, etc. The bits/ctype_base.h +upper-case, lower-case, alphabetic, etc. The ctype_base.h file gives the type of the integer, and the values of the various bit masks. You will have to peer at your own <ctype.h> to figure out how to define the values required by this file. -

The bits/ctype_base.h header file does not need include guards. +

The ctype_base.h header file does not need include guards. It should contain a single struct definition called ctype_base. This struct should contain two type declarations, and one enumeration declaration, like this example, taken @@ -223,9 +223,9 @@ but you must still define the type. example, using the values from your native <ctype.h>. They can be given symbolically (as above), or numerically, if you prefer. You do not have to include <ctype.h> in this header; it will always be -included before bits/ctype_base.h is included. +included before ctype_base.h is included. -

The next file to write is bits/ctype_noninline.h, which also does +

The next file to write is ctype_noninline.h, which also does not require include guards. This file defines a few member functions that will be included in include/bits/locale_facets.h. The first function that must be written is the ctype<char>::ctype @@ -296,7 +296,7 @@ ctype<char>::do_tolower(char* __low, const char* __high) const } -

You must also provide the bits/ctype_inline.h file, which +

You must also provide the ctype_inline.h file, which contains a few more functions. On most systems, you can just copy config/os/generic/ctype_inline.h and use it on your system. @@ -355,9 +355,9 @@ scan_not(mask __m, const char* __low, const char* __high) const throw()

Node:Thread safety, -Next:, -Previous:Character types, -Up:Top +Next:, +Previous:Character types, +Up:Top

Thread safety

@@ -372,11 +372,11 @@ multi-threaded. are two distinct approaches. One is to provide a version for your CPU, using assembly language constructs. The other is to use the thread-safety primitives in your operating system. In either case, you -make a file called bits/atomicity.h, and the variable +make a file called atomicity.h, and the variable ATOMICITYH must point to this file.

If you are using the assembly-language approach, put this code in -config/cpu/<chip>/bits/atomicity.h, where chip is the name of +config/cpu/<chip>/atomicity.h, where chip is the name of your processor (see CPU). No additional changes are necessary to locate the file in this case; ATOMICITYH will be set by default. @@ -394,7 +394,7 @@ the appropriate os_include_dir. For examples of this approach, see the atomicity.h file for AIX.

With those bits out of the way, you have to actually write -bits/atomicity.h itself. This file should be wrapped in an +atomicity.h itself. This file should be wrapped in an include guard named _BITS_ATOMICITY_H. It should define one type, and two functions. @@ -430,9 +430,9 @@ __atomic_add (_Atomic_word* __mem, int __val)

Node:Numeric limits, -Next:, -Previous:Thread safety, -Up:Top +Next:, +Previous:Thread safety, +Up:Top

Numeric limits

@@ -453,9 +453,9 @@ your CPU configuration directory (see CPU).

Node:Libtool, -Next:, -Previous:Numeric limits, -Up:Top +Next:, +Previous:Numeric limits, +Up:Top

Libtool

@@ -489,8 +489,8 @@ operating system.

Node:GNU Free Documentation License, -Previous:Libtool, -Up:Top +Previous:Libtool, +Up:Top

GNU Free Documentation License

diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index 611f83b147e..b8254b9a040 100644 --- a/libstdc++-v3/docs/html/faq/index.html +++ b/libstdc++-v3/docs/html/faq/index.html @@ -112,7 +112,7 @@ as described in chapters 17 through 27 and annex D. As the library reaches stable plateaus, it is captured in a snapshot and released. The current release is - the + the fourteenth snapshot. For those who want to see exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source is available over @@ -170,8 +170,8 @@

1.4 How do I get libstdc++?

The fourteenth (and latest) snapshot of libstdc++-v3 is - available via - ftp. + available + via ftp.

The homepage has instructions for retrieving the latest CVS sources, and for diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index 9a37bb79999..76a954458f9 100644 --- a/libstdc++-v3/docs/html/faq/index.txt +++ b/libstdc++-v3/docs/html/faq/index.txt @@ -869,13 +869,13 @@ References 46. ../faq/index.html#5_6 47. ../faq/index.html#5_7 48. ../faq/index.html#5_8 - 49. http://gcc.gnu.org/libstdc++/download.html + 49. http://gcc.gnu.org/libstdc++/index.html#download 50. ../faq/index.html#4_4_interface 51. ../17_intro/DESIGN 52. http://gcc.gnu.org/ 53. http://gcc.gnu.org/gcc-3.0/buildstat.html 54. http://gcc.gnu.org/libstdc++/ - 55. http://gcc.gnu.org/libstdc++/download.html + 55. http://gcc.gnu.org/libstdc++/index.html#download 56. http://gcc.gnu.org/libstdc++/ 57. ../17_intro/contribute.html 58. http://www.boost.org/