From patchwork Tue Jun 25 12:38:37 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Jonathan Wakely X-Patchwork-Id: 1952105 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=ff2gDhR9; dkim-atps=neutral Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=gcc.gnu.org (client-ip=8.43.85.97; helo=server2.sourceware.org; envelope-from=gcc-patches-bounces+incoming=patchwork.ozlabs.org@gcc.gnu.org; receiver=patchwork.ozlabs.org) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4W7kvT3q2Qz20Z9 for ; Tue, 25 Jun 2024 22:40:37 +1000 (AEST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CA1983841884 for ; Tue, 25 Jun 2024 12:40:35 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 105AE386D61E for ; Tue, 25 Jun 2024 12:40:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 105AE386D61E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 105AE386D61E Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1719319205; cv=none; b=OPirHVm0pUT9HLyc6TV1rVMWNrWkqwm5/KH6wa54fe5fgoyEExFSXV0E5Ks1SFZszqeNdfNnGPoZUHw/FkrDiffynY45eK8yyxKxgKZxGgtm2vnTnIqz0zTrIqoUQfjBdtt/JetzBfzmei8TTrzHuDZWyIhYFnMjwY3daMDmEAI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1719319205; c=relaxed/simple; bh=blYrkkZvWIMIF3XumUAQ8PAGwe6WV3HcIE+J2TkNSXs=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=FSWE/TvvL5elH+qtNd2E1eZnKpmaVtO5L9mwvNNutuco6DJbeU683JojW6tZ6lp/DrROAhr8HqYxs8CWUZ7Jkkhn/wJ2uLEqN+XB7iln69ESHpKDixc6kMNfSpFhD4QG0Emi9k6jZviJVlmZJ9GO8chTq2pYQIYmCmlYUgSFgLY= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1719319201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6ITOiG2XT6rwyd66rRzXj+CKwmakHaHOEzUd//nmXkA=; b=ff2gDhR9LZH+DZ65xuh5vaP0oQebeAJ3q/4Cw7fD2Ufu3eEd8s/QGJct+q7r6M101i3DGb USOxji6vsj9C63Mo45wb/OrmAym6sUYiWQxV/p4tmkOIAZzf8cWygozwtDNsiNfM0/73SY ZqEbtU+RpCPigC/ek/8onn8CFl9Kffs= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-339-Xl7-qK1WNS2UMhId--9f8g-1; Tue, 25 Jun 2024 08:39:56 -0400 X-MC-Unique: Xl7-qK1WNS2UMhId--9f8g-1 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id B285A19560A7; Tue, 25 Jun 2024 12:39:50 +0000 (UTC) Received: from localhost (unknown [10.42.28.182]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id A533219560B2; Tue, 25 Jun 2024 12:39:43 +0000 (UTC) From: Jonathan Wakely To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Cc: Gerald Pfeifer Subject: [PATCH] libstdc++: Replace viewcvs links in docs with cgit links Date: Tue, 25 Jun 2024 13:38:37 +0100 Message-ID: <20240625123942.2530210-1-jwakely@redhat.com> In-Reply-To: <496d3f69-26c2-2aea-2099-c93df4158aa6@pfeifer.com> References: <496d3f69-26c2-2aea-2099-c93df4158aa6@pfeifer.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com X-Spam-Status: No, score=-10.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_SHORT, PP_MIME_FAKE_ASCII_TEXT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, RCVD_IN_SBL_CSS, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gcc-patches-bounces+incoming=patchwork.ozlabs.org@gcc.gnu.org Gerald noticed these stale viewcvs links. I'll push this to trunk later this week, and backport too. -- >8 -- libstdc++-v3/ChangeLog: * doc/xml/faq.xml: Replace viewcvs links with cgit links. * doc/xml/manual/allocator.xml: Likewise. * doc/xml/manual/mt_allocator.xml: Likewise. * doc/html/*: Regenerate. --- libstdc++-v3/doc/html/api.html | 2 +- libstdc++-v3/doc/html/faq.html | 2 +- libstdc++-v3/doc/html/manual/memory.html | 10 +++++----- libstdc++-v3/doc/html/manual/mt_allocator_impl.html | 6 +++--- libstdc++-v3/doc/xml/faq.xml | 2 +- libstdc++-v3/doc/xml/manual/allocator.xml | 10 +++++----- libstdc++-v3/doc/xml/manual/mt_allocator.xml | 6 +++--- 7 files changed, 19 insertions(+), 19 deletions(-) diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html index b494d91f9af..d2cff093d8f 100644 --- a/libstdc++-v3/doc/html/api.html +++ b/libstdc++-v3/doc/html/api.html @@ -38,4 +38,4 @@

In addition, a rendered set of man pages are available in the same location specified above. Start with C++Intro(3). -

Prev Up Next
 Home 
+

Prev Up Next
 Home 
\ No newline at end of file diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index dcb94ba67dc..507555839f2 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -147,7 +147,7 @@ The libstdc++ project is contributed to by several developers all over the world, in the same way as GCC or the Linux kernel. The current maintainers are listed in the - MAINTAINERS + MAINTAINERS file (look for "c++ runtime libs").

Development and discussion is held on the libstdc++ mailing diff --git a/libstdc++-v3/doc/html/manual/memory.html b/libstdc++-v3/doc/html/manual/memory.html index 08ad2fd4dd8..6b707105969 100644 --- a/libstdc++-v3/doc/html/manual/memory.html +++ b/libstdc++-v3/doc/html/manual/memory.html @@ -120,8 +120,8 @@ Over multiple iterations, various STL container objects have elements inserted to some maximum amount. A variety of allocators are tested. - Test source for sequence - and associative + Test source for sequence + and associative containers.

  • Insertion and erasure in a multi-threaded environment. @@ -130,14 +130,14 @@ on a per-thread basis, as well as measuring thread contention for memory resources. Test source - here. + here.

  • A threaded producer/consumer model.

    Test source for - sequence + sequence and - associative + associative containers.

    • Since GCC 12 the default choice for diff --git a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html index 2e5926add00..c69b9c5b55a 100644 --- a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html +++ b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html @@ -155,7 +155,7 @@ that uses it is fully constructed. For most (but not all) STL containers, this works, as an instance of the allocator is constructed as part of a container's constructor. However, this assumption is implementation-specific, and subject to change. For an example of a -pool that frees memory, see the following - - example. +pool that frees memory, see the + ext/mt_allocator/deallocate_local-6.cc + example.

    Prev Up Next
    Design Issues Home Single Thread Example
    \ No newline at end of file diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index 4888fa93ae9..bccbb98a5a3 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -90,7 +90,7 @@ The libstdc++ project is contributed to by several developers all over the world, in the same way as GCC or the Linux kernel. The current maintainers are listed in the - MAINTAINERS + MAINTAINERS file (look for "c++ runtime libs"). diff --git a/libstdc++-v3/doc/xml/manual/allocator.xml b/libstdc++-v3/doc/xml/manual/allocator.xml index 2418539be8d..7e74dca404a 100644 --- a/libstdc++-v3/doc/xml/manual/allocator.xml +++ b/libstdc++-v3/doc/xml/manual/allocator.xml @@ -184,8 +184,8 @@ Over multiple iterations, various STL container objects have elements inserted to some maximum amount. A variety of allocators are tested. - Test source for sequence - and associative + Test source for sequence + and associative containers. @@ -200,7 +200,7 @@ on a per-thread basis, as well as measuring thread contention for memory resources. Test source - here. + here. @@ -210,9 +210,9 @@ Test source for - sequence + sequence and - associative + associative containers. diff --git a/libstdc++-v3/doc/xml/manual/mt_allocator.xml b/libstdc++-v3/doc/xml/manual/mt_allocator.xml index f1c09b3bd8f..81d819d70d5 100644 --- a/libstdc++-v3/doc/xml/manual/mt_allocator.xml +++ b/libstdc++-v3/doc/xml/manual/mt_allocator.xml @@ -307,9 +307,9 @@ that uses it is fully constructed. For most (but not all) STL containers, this works, as an instance of the allocator is constructed as part of a container's constructor. However, this assumption is implementation-specific, and subject to change. For an example of a -pool that frees memory, see the following - - example. +pool that frees memory, see the + ext/mt_allocator/deallocate_local-6.cc + example.