From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2153) id 493FA3987900; Thu, 17 Sep 2020 17:00:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 493FA3987900 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1600362048; bh=JYR4AebylCinHwKbF+/X7IlK4RQ+J9u94fEwKZvATIk=; h=From:To:Subject:Date:From; b=MtUXDovBVFA0Qx+ItGdthJf3lWAXHK0mgcDnrvZpN0oc4rnRo/rJbMw1s9/5spJPE wzNCTmXnRiwoVJw7MD8PF+D+HSkIIo2SoKIz+5c0qt9XaYh18BZghwi8Vhn+vBn2Te uo/uzscalfU6JXjigLaTvlRRDH6fcxpOATDSUICE= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" From: Jakub Jelinek To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] libstdc++: Fix broken link to SGI STL FAQ X-Act-Checkin: gcc X-Git-Author: Jonathan Wakely X-Git-Refname: refs/vendors/redhat/heads/gcc-8-branch X-Git-Oldrev: 74c39479b914ac2069617a8b04d1747dadb1c236 X-Git-Newrev: 23e0d591d3db6a60c21a9a1bc4968313c3262369 Message-Id: <20200917170048.493FA3987900@sourceware.org> Date: Thu, 17 Sep 2020 17:00:48 +0000 (GMT) X-BeenThere: libstdc++-cvs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2020 17:00:48 -0000 https://gcc.gnu.org/g:23e0d591d3db6a60c21a9a1bc4968313c3262369 commit 23e0d591d3db6a60c21a9a1bc4968313c3262369 Author: Jonathan Wakely Date: Mon May 4 22:54:25 2020 +0100 libstdc++: Fix broken link to SGI STL FAQ The previous URL to an entry in the wayback machine now redirects to a page saying "SGI.com Tech Archive Resources now retired" so use an older entry from the archive. * doc/xml/faq.xml: Use working link for SGI STL FAQ. * doc/html/*: Regenerate. Diff: --- libstdc++-v3/ChangeLog | 5 ++ libstdc++-v3/doc/html/faq.html | 26 ++++----- libstdc++-v3/doc/xml/faq.xml | 118 ++++++++++++++++++++--------------------- 3 files changed, 77 insertions(+), 72 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 8d3f7f9b185..30b1561b954 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,8 @@ +2020-05-04 Jonathan Wakely + + * doc/xml/faq.xml: Use working link for SGI STL FAQ. + * doc/html/*: Regenerate. + 2020-04-21 Jonathan Wakely * doc/xml/manual/status_cxx2017.xml: Fix name of feature test macro. diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index ac99835acf2..18407225d7a 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -194,7 +194,7 @@ information is available on the homepage (including how to browse the list archives); to send a message to the list, use . -

+

If you have a question that you think should be included here, or if you have a question about a question/answer here, please send email to the libstdc++ mailing list, as above. @@ -246,8 +246,8 @@ development tools. It may be necessary to install extra development packages to get the headers, or the documentation, or the source: please consult your vendor for details. -

- To build and install from the GNU GCC sources, please consult the +

+ To build and install from the GNU GCC sources, please consult the setup documentation for detailed instructions. You may wish to browse those files ahead @@ -268,7 +268,7 @@

Libstdc++ comes with its own validation testsuite, which includes conformance testing, regression testing, ABI testing, and - performance testing. Please consult the + performance testing. Please consult the testing documentation for GCC and Testing in the libstdc++ @@ -424,12 +424,12 @@

Note

This answer is old and probably no longer be relevant.

By default we try to support the C99 long long type. This requires that certain functions from your C library be present. -

+

Up through release 3.0.2 the platform-specific tests performed by libstdc++ were too general, resulting in a conservative approach to enabling the long long code paths. The most commonly reported platform affected was Solaris. -

+

This has been fixed for libstdc++ releases greater than 3.0.3.

4.3.

_XOPEN_SOURCE and _GNU_SOURCE are always defined? @@ -484,7 +484,7 @@ and later. A patch went in just after the 3.3 release to make mips* use the generic implementation instead. You can also configure for mipsel-elf as a workaround. -

+

The mips*-*-linux* port continues to use the MIPS II routines, and more work in this area is expected.

4.7.

@@ -510,7 +510,7 @@ enable wchar_t and C++ library structures like wstring were present. This impacted Solaris, Darwin, and BSD variants, and is fixed in libstdc++ versions post 4.1.0. -

+

5.1. What works already?
5.2. @@ -526,8 +526,8 @@ platforms. Also dependent on the underlying platform is support for wchar_t and long long specializations, and details of thread support. -

- Long answer: See the implementation status pages for +

+ Long answer: See the implementation status pages for C++98, TR1, C++11, @@ -536,7 +536,7 @@

5.2.

Bugs in the ISO C++ language or library specification

- Unfortunately, there are some. + Unfortunately, there are some.

For those people who are not part of the ISO Library Group (i.e., nearly all of us needing to read this page in the first @@ -560,7 +560,7 @@ or an older version of the GNU compilers. Third, you can find more information on the libstdc++ and the GCC mailing lists: search these lists with terms describing your issue. -

+

Before reporting a bug, please examine the bugs database, with the component set to “c++”. @@ -813,7 +813,7 @@ and backwards compatibility documentation.

- The FAQ + The FAQ for SGI's STL is still recommended reading.

7.4.

Extensions and Backward Compatibility diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index aff6c8d6004..cf8684e1cea 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -2,9 +2,9 @@

- + Frequently Asked Questions - + 2008-2018 @@ -36,7 +36,7 @@ exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source can be cloned via Git. - + N.B. The library is called libstdc++ not stdlibc++. @@ -58,7 +58,7 @@ (as the Draft Standard used to say) incomplet and incorrekt, and many suffered from limitations of the compilers that used them. - + The GNU compiler collection (gcc, g++, etc) is widely @@ -68,7 +68,7 @@ the rapid development and near-legendary portability that are the hallmarks of an open-source project are applied to libstdc++. - + All of the standard classes and functions from C++98/C++03, C++11 and C++14 (such as string, @@ -100,7 +100,7 @@ archives, is open to everyone. You can read instructions for doing so on the GCC mailing lists page. If you have questions, ideas, code, or are just curious, sign up! - + @@ -115,7 +115,7 @@ Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help. - + @@ -135,7 +135,7 @@ anybody who is willing to help write documentation, for example, or has found a bug in code that we all thought was working and is willing to provide details, is more than welcome! - + @@ -152,7 +152,7 @@ being developed. It should not be used for new projects, and won't even compile with recent releases of GCC (or most other C++ compilers). - + More information can be found in the Backwards @@ -175,13 +175,13 @@ information is available on the homepage (including how to browse the list archives); to send a message to the list, use libstdc++@gcc.gnu.org. - + - + If you have a question that you think should be included here, or if you have a question about a question/answer here, please send email to the libstdc++ mailing list, as above. - + @@ -201,7 +201,7 @@ See our license description for these and related questions. - + @@ -215,7 +215,7 @@ No. The special exception permits use of the library in proprietary applications. - + @@ -235,7 +235,7 @@ are expanded inside the code that uses the library. So to allow people to replace the library code, someone using the library would have to distribute their own source, rendering the LGPL equivalent to the GPL. - + @@ -249,7 +249,7 @@ None. We encourage such programs to be released as free software, but we won't punish you or sue you if you choose otherwise. - + @@ -271,14 +271,14 @@ development tools. It may be necessary to install extra development packages to get the headers, or the documentation, or the source: please consult your vendor for details. - - - To build and install from the GNU GCC sources, please consult the + + + To build and install from the GNU GCC sources, please consult the setup documentation for detailed instructions. You may wish to browse those files ahead of time to get a feel for what's required. - + @@ -313,12 +313,12 @@ Libstdc++ comes with its own validation testsuite, which includes conformance testing, regression testing, ABI testing, and - performance testing. Please consult the + performance testing. Please consult the testing documentation for GCC and Testing in the libstdc++ manual for more details. - + If you find bugs in the testsuite programs themselves, or if you think of a new test program that should be added to the suite, @@ -432,7 +432,7 @@ using anything from the rest of the library, such as IOStreams or vectors, then you'll still need pieces from libstdc++.a. - + @@ -465,7 +465,7 @@ is only possible to a certain extent; the object files in question contain template classes and template functions, pre-instantiated, and splitting those up causes severe maintenance headaches. - + On supported platforms, libstdc++ takes advantage of garbage collection in the GNU linker to get a result similar to separating @@ -495,12 +495,12 @@ Perhaps. - + Since the goal of ISO Standardization is for all C++ implementations to be able to share code, libstdc++ should be usable under any ISO-compliant compiler, at least in theory. - + However, the reality is that libstdc++ is targeted and optimized for GCC/G++. This means that often libstdc++ uses specific, @@ -515,7 +515,7 @@ been known to work with versions of the EDG C++ compiler, and vendor-specific proprietary C++ compilers such as the Intel ICC C++ compiler. - + @@ -533,16 +533,16 @@ By default we try to support the C99 long long type. This requires that certain functions from your C library be present. - - + + Up through release 3.0.2 the platform-specific tests performed by libstdc++ were too general, resulting in a conservative approach to enabling the long long code paths. The most commonly reported platform affected was Solaris. - - + + This has been fixed for libstdc++ releases greater than 3.0.3. - + @@ -651,10 +651,10 @@ make mips* use the generic implementation instead. You can also configure for mipsel-elf as a workaround. - + The mips*-*-linux* port continues to use the MIPS II routines, and more work in this area is expected. - + @@ -700,9 +700,9 @@ enable wchar_t and C++ library structures like wstring were present. This impacted Solaris, Darwin, and BSD variants, and is fixed in libstdc++ versions post 4.1.0. - - - + + + @@ -728,14 +728,14 @@ for wchar_t and long long specializations, and details of thread support. - - Long answer: See the implementation status pages for + + Long answer: See the implementation status pages for C++98, TR1, C++11, C++14, and C++17. - + @@ -747,7 +747,7 @@ - Unfortunately, there are some. + Unfortunately, there are some. For those people who are not part of the ISO Library Group @@ -758,7 +758,7 @@ website. Many of these issues have resulted in code changes in libstdc++. - + If you think you've discovered a new bug that is not listed, please post a message describing your problem to the author of @@ -784,12 +784,12 @@ or an older version of the GNU compilers. Third, you can find more information on the libstdc++ and the GCC mailing lists: search these lists with terms describing your issue. - - + + Before reporting a bug, please examine the bugs database, with the component set to c++. - + @@ -824,7 +824,7 @@ fs.close(); fs.open("a_new_file"); - + All operations on the re-opened fs would fail, or at least act very strangely, especially if fs reached the @@ -840,7 +840,7 @@ of DR #409 and open() now calls clear() on success. - + @@ -859,7 +859,7 @@ necessarily trying to be OO. The option also enforces outdated guidelines from old editions of the books, and the advice isn't all relevant to modern C++ (especially C++11 and later). - + We do, however, try to have libstdc++ sources as clean as possible. If you see some simple changes that pacify @@ -889,7 +889,7 @@ sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. - + @@ -947,7 +947,7 @@ checks, is available in the Diagnostics. chapter of the manual. - + @@ -1013,7 +1013,7 @@ want to test the library for memory leaks please read Tips for memory leak hunting first. - + @@ -1028,7 +1028,7 @@ See the Containers chapter. - + @@ -1056,7 +1056,7 @@ fixes. Bugs have a way of being reintroduced; if an old bug creeps back in, it will be caught immediately by the testsuite - but only if such a test exists. - + @@ -1150,9 +1150,9 @@ compatibility documentation. - The FAQ + The FAQ for SGI's STL is still recommended reading. - + @@ -1165,7 +1165,7 @@ See the link on backwards compatibility and link on evolution. - + @@ -1206,7 +1206,7 @@ Please refer to the Contributing section in our manual. - + @@ -1272,7 +1272,7 @@ so they may later be changed. Deciding which, and implementing the decisions, must happen before you can reasonably document a candidate C++ ABI that encompasses the standard library. - + @@ -1302,7 +1302,7 @@ See Shrink-to-fit strings for a similar solution for strings. - +