* www.sgi.com/tech/stl/ is gone
@ 2018-03-18 23:37 Gerald Pfeifer
2018-03-19 0:20 ` Joel Sherrill
2018-03-19 17:12 ` Jonathan Wakely
0 siblings, 2 replies; 4+ messages in thread
From: Gerald Pfeifer @ 2018-03-18 23:37 UTC (permalink / raw)
To: libstdc++; +Cc: gcc
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
...redirecting to a dummy page. Unfortunately there are a fair
number of references in the libstdc++ docs, see below.
I'll take care of anything outside of libstdc++; can you please
have a look as far as the libstdc++ docs go?
Gerald
http://gcc.gnu.org/onlinedocs/libstdc++/faq.html
â¡ http://www.sgi.com/tech/stl/
â¡ http://www.sgi.com/tech/stl/FAQ.html
â¡ http://www.sgi.com/tech/stl/whats_new.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode_design.html
â¡ http://www.sgi.com/tech/stl/
http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_numerics.html
â¡ http://www.sgi.com/tech/stl/iota.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_sgi.html
â¡ http://www.sgi.com/tech/stl/HashFunction.html
â¡ http://www.sgi.com/tech/stl/hash.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/policy_data_structures.html
â¡ http://www.sgi.com/tech/stl/
http://gcc.gnu.org/onlinedocs/libstdc++/manual/using_concurrency.html
â¡ http://www.sgi.com/tech/stl/Allocators.html
â¡ http://www.sgi.com/tech/stl/thread_safety.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/utilities.html
â¡ http://www.sgi.com/tech/stl/functors.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: www.sgi.com/tech/stl/ is gone
2018-03-18 23:37 www.sgi.com/tech/stl/ is gone Gerald Pfeifer
@ 2018-03-19 0:20 ` Joel Sherrill
2018-03-19 17:12 ` Jonathan Wakely
1 sibling, 0 replies; 4+ messages in thread
From: Joel Sherrill @ 2018-03-19 0:20 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: libstdc++, gcc
On Mar 18, 2018 6:37 PM, "Gerald Pfeifer" <gerald@pfeifer.com> wrote:
...redirecting to a dummy page. Unfortunately there are a fair
number of references in the libstdc++ docs, see below.
I'll take care of anything outside of libstdc++; can you please
have a look as far as the libstdc++ docs go?
Is cppreference.com an appropriate place to link to?
--joel
Gerald
http://gcc.gnu.org/onlinedocs/libstdc++/faq.html
□ http://www.sgi.com/tech/stl/
□ http://www.sgi.com/tech/stl/FAQ.html
□ http://www.sgi.com/tech/stl/whats_new.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode_design.html
□ http://www.sgi.com/tech/stl/
http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_numerics.html
□ http://www.sgi.com/tech/stl/iota.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_sgi.html
□ http://www.sgi.com/tech/stl/HashFunction.html
□ http://www.sgi.com/tech/stl/hash.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/policy_data_structures.html
□ http://www.sgi.com/tech/stl/
http://gcc.gnu.org/onlinedocs/libstdc++/manual/using_concurrency.html
□ http://www.sgi.com/tech/stl/Allocators.html
□ http://www.sgi.com/tech/stl/thread_safety.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/utilities.html
□ http://www.sgi.com/tech/stl/functors.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: www.sgi.com/tech/stl/ is gone
2018-03-18 23:37 www.sgi.com/tech/stl/ is gone Gerald Pfeifer
2018-03-19 0:20 ` Joel Sherrill
@ 2018-03-19 17:12 ` Jonathan Wakely
2018-04-10 19:28 ` Jonathan Wakely
1 sibling, 1 reply; 4+ messages in thread
From: Jonathan Wakely @ 2018-03-19 17:12 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: libstdc++, gcc
On 18 March 2018 at 23:37, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> ...redirecting to a dummy page. Unfortunately there are a fair
> number of references in the libstdc++ docs, see below.
>
> I'll take care of anything outside of libstdc++; can you please
> have a look as far as the libstdc++ docs go?
>
> Gerald
>
>
> http://gcc.gnu.org/onlinedocs/libstdc++/faq.html
>
> □ http://www.sgi.com/tech/stl/
> □ http://www.sgi.com/tech/stl/FAQ.html
> □ http://www.sgi.com/tech/stl/whats_new.html
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode_design.html
>
> □ http://www.sgi.com/tech/stl/
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_numerics.html
>
> □ http://www.sgi.com/tech/stl/iota.html
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_sgi.html
>
> □ http://www.sgi.com/tech/stl/HashFunction.html
> □ http://www.sgi.com/tech/stl/hash.html
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/policy_data_structures.html
>
> □ http://www.sgi.com/tech/stl/
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/using_concurrency.html
>
> □ http://www.sgi.com/tech/stl/Allocators.html
> □ http://www.sgi.com/tech/stl/thread_safety.html
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/utilities.html
>
> □ http://www.sgi.com/tech/stl/functors.html
I suggest we use the archived copy at
https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: www.sgi.com/tech/stl/ is gone
2018-03-19 17:12 ` Jonathan Wakely
@ 2018-04-10 19:28 ` Jonathan Wakely
0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Wakely @ 2018-04-10 19:28 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: libstdc++, gcc
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
On 19 March 2018 at 17:12, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 18 March 2018 at 23:37, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>> ...redirecting to a dummy page. Unfortunately there are a fair
>> number of references in the libstdc++ docs, see below.
>>
>> I'll take care of anything outside of libstdc++; can you please
>> have a look as far as the libstdc++ docs go?
>>
>> Gerald
>>
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/faq.html
>>
>> □ http://www.sgi.com/tech/stl/
>> □ http://www.sgi.com/tech/stl/FAQ.html
>> □ http://www.sgi.com/tech/stl/whats_new.html
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode_design.html
>>
>> □ http://www.sgi.com/tech/stl/
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_numerics.html
>>
>> □ http://www.sgi.com/tech/stl/iota.html
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_sgi.html
>>
>> □ http://www.sgi.com/tech/stl/HashFunction.html
>> □ http://www.sgi.com/tech/stl/hash.html
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/policy_data_structures.html
>>
>> □ http://www.sgi.com/tech/stl/
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/using_concurrency.html
>>
>> □ http://www.sgi.com/tech/stl/Allocators.html
>> □ http://www.sgi.com/tech/stl/thread_safety.html
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/utilities.html
>>
>> □ http://www.sgi.com/tech/stl/functors.html
>
> I suggest we use the archived copy at
> https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/
Done with this patch (I will regenerate the HTML after some more doc changes).
Committed to trunk, backports to follow.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 11049 bytes --]
commit 719e805c69e3ebb653ab0cc179b149ee54870807
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Apr 10 16:46:58 2018 +0100
Update links to archived copy of SGI STL docs
* doc/xml/faq.xml: Update links to archived copy of SGI STL docs.
* doc/xml/manual/backwards_compatibility.xml: Likewise.
* doc/xml/manual/containers.xml: Likewise.
* doc/xml/manual/debug_mode.xml: Likewise.
* doc/xml/manual/extensions.xml: Likewise.
* doc/xml/manual/policy_data_structures_biblio.xml: Likewise.
* doc/xml/manual/using.xml: Likewise.
* doc/xml/manual/utilities.xml: Likewise.
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 3e315e2d5ba..b0b1f98e641 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -1132,9 +1132,9 @@
</para>
<para>
Libstdc++-v3 incorporates a lot of code from
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/">the SGI STL</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/">the SGI STL</link>
(the final merge was from
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/whats_new.html">release 3.3</link>).
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/whats_new.html">release 3.3</link>).
The code in libstdc++ contains many fixes and changes compared to the
original SGI code.
</para>
@@ -1153,7 +1153,7 @@
compatibility</link> documentation.
</para>
<para>
- The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/FAQ.html">FAQ</link>
+ The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/FAQ.html">FAQ</link>
for SGI's STL is still recommended reading.
</para>
</answer>
diff --git a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
index dbb33719fb3..aa95f3eb1c9 100644
--- a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
+++ b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
@@ -536,7 +536,7 @@ particular <quote>info iostream</quote>.
against the gthr.h abstraction layer which is provided by gcc. A
minor problem that pops up every so often is different
interpretations of what "thread-safe" means for a
- library (not a general program). We currently use the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/thread_safety.html">same
+ library (not a general program). We currently use the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/thread_safety.html">same
definition that SGI</link> uses for their STL subset. However,
the exception for read-only containers only applies to the STL
components. This definition is widely-used and something similar
diff --git a/libstdc++-v3/doc/xml/manual/containers.xml b/libstdc++-v3/doc/xml/manual/containers.xml
index e81c7f06875..5c9854efbdd 100644
--- a/libstdc++-v3/doc/xml/manual/containers.xml
+++ b/libstdc++-v3/doc/xml/manual/containers.xml
@@ -28,7 +28,7 @@
Yes it is, at least using the <xref linkend="manual.intro.using.abi">old
ABI</xref>, and that's okay. This is a decision that we preserved
when we imported SGI's STL implementation. The following is
- quoted from <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/FAQ.html">their FAQ</link>:
+ quoted from <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/FAQ.html">their FAQ</link>:
</para>
<blockquote>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/debug_mode.xml b/libstdc++-v3/doc/xml/manual/debug_mode.xml
index 65abf051674..5082bbfb724 100644
--- a/libstdc++-v3/doc/xml/manual/debug_mode.xml
+++ b/libstdc++-v3/doc/xml/manual/debug_mode.xml
@@ -858,7 +858,7 @@ test02()
standard library implementations.</para></listitem>
<listitem><para><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.stlport.org/">STLport</link>: STLport is a free
- implementation of the C++ standard library derived from the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/">SGI implementation</link>, and
+ implementation of the C++ standard library derived from the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/">SGI implementation</link>, and
ported to many other platforms. It includes a debug mode that uses a
wrapper model (that in some ways inspired the libstdc++ debug mode
design), although at the time of this writing the debug mode is
diff --git a/libstdc++-v3/doc/xml/manual/extensions.xml b/libstdc++-v3/doc/xml/manual/extensions.xml
index a6e4db2b6f7..84a995a5a7d 100644
--- a/libstdc++-v3/doc/xml/manual/extensions.xml
+++ b/libstdc++-v3/doc/xml/manual/extensions.xml
@@ -227,12 +227,12 @@ extensions, be aware of two things:
</para>
<para>Each of the associative containers map, multimap, set, and multiset
have a counterpart which uses a
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/HashFunction.html">hashing
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/HashFunction.html">hashing
function</link> to do the arranging, instead of a strict weak ordering
function. The classes take as one of their template parameters a
function object that will return the hash value; by default, an
instantiation of
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/hash.html">hash</link>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/hash.html">hash</link>.
You should specialize this functor for your class, or define your own,
before trying to use one of the hashing classes.
</para>
@@ -394,7 +394,7 @@ get_temporary_buffer(5, (int*)0);
</para>
<para>The <code>iota</code> function wins the award for Extension With the
Coolest Name (the name comes from Ken Iverson's APL language.) As
- described in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/iota.html">SGI
+ described in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/iota.html">SGI
documentation</link>, it "assigns sequentially increasing values to a range.
That is, it assigns <code>value</code> to <code>*first</code>,
<code>value + 1</code> to<code> *(first + 1)</code> and so on."
diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
index 1becbc2956a..1a6e14a5a10 100644
--- a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
+++ b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
@@ -1206,7 +1206,7 @@
<biblioentry xml:id="biblio.sgi_stl">
<title>
<link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://www.sgi.com/tech/stl/">
+ xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/">
Standard Template Library Programmer's Guide
</link>
</title>
diff --git a/libstdc++-v3/doc/xml/manual/using.xml b/libstdc++-v3/doc/xml/manual/using.xml
index fdbaa573007..bb04e0f76c9 100644
--- a/libstdc++-v3/doc/xml/manual/using.xml
+++ b/libstdc++-v3/doc/xml/manual/using.xml
@@ -1507,7 +1507,7 @@ The standard places requirements on the library to ensure that no data
races are caused by the library itself or by programs which use the
library correctly (as described below).
The C++11 memory model and library requirements are a more formal version
-of the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/thread_safety.html">SGI STL</link> definition of thread safety, which the library used
+of the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/thread_safety.html">SGI STL</link> definition of thread safety, which the library used
prior to the 2011 standard.
</para>
@@ -1780,10 +1780,10 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
</para>
<para>Two excellent pages to read when working with the Standard C++
containers and threads are
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/thread_safety.html">SGI's
- http://www.sgi.com/tech/stl/thread_safety.html</link> and
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/Allocators.html">SGI's
- http://www.sgi.com/tech/stl/Allocators.html</link>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/thread_safety.html">SGI's
+ https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/thread_safety.html</link> and
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/Allocators.html">SGI's
+ https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/Allocators.html</link>.
</para>
<para><emphasis>However, please ignore all discussions about the user-level
configuration of the lock implementation inside the STL
diff --git a/libstdc++-v3/doc/xml/manual/utilities.xml b/libstdc++-v3/doc/xml/manual/utilities.xml
index 6a4a792ca1a..469d85f4109 100644
--- a/libstdc++-v3/doc/xml/manual/utilities.xml
+++ b/libstdc++-v3/doc/xml/manual/utilities.xml
@@ -22,8 +22,8 @@
get slightly the wrong idea. In the interest of not reinventing
the wheel, we will refer you to the introduction to the functor
concept written by SGI as part of their STL, in
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.sgi.com/tech/stl/functors.html">their
- http://www.sgi.com/tech/stl/functors.html</link>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/functors.html">their
+ https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/functors.html</link>.
</para>
</section>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-04-10 15:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-18 23:37 www.sgi.com/tech/stl/ is gone Gerald Pfeifer
2018-03-19 0:20 ` Joel Sherrill
2018-03-19 17:12 ` Jonathan Wakely
2018-04-10 19:28 ` Jonathan Wakely
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).