From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) by sourceware.org (Postfix) with ESMTPS id A23673891018; Mon, 12 Jul 2021 17:18:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A23673891018 Received: by mail-ot1-x332.google.com with SMTP id i12-20020a05683033ecb02903346fa0f74dso19586152otu.10; Mon, 12 Jul 2021 10:18:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CmHZSVN4k22S5zYb1Dem07702eTAVjQfrJ3YRz4LulM=; b=oZ8l+s0EhU/bPZGPtdsgKByOQmlj1n5c3Jm9wNNIJAldlP/tLbV74ODph798rCKV/G h5zqPpGia8hOGaDQSR8QH6/mbokmQi76I7Z5e2pCbAWSGGM6kh+4KFgIFe5qVe2KvI+S cmS7lCUMj4yaoTVd8DZT4YCufSMiwxtOfDjuVOYR+EOTOly0swiQgGsO7RsoV3MghIh5 E/shOli7+ytK8Ng8H08xa1vt1hZyr3lj4rf+kiUinpHOIWm/9SS7jfP+cEha/N3nmXpj IL/h+SD6SkHN4xhjzf+EFFQBs/liLi5E8nhOStpVIfzskTP3nTG8+6AXZ08NrJ15ZrqW eiIg== X-Gm-Message-State: AOAM530a9HseSsD+tVD5uWLAYocwPWadsvolzcYvsdb9tUXY8096CDFM Qq35bzyBswgLrh3qGEv9Eypf/U3rllg= X-Google-Smtp-Source: ABdhPJwNJWnQI4d/NP47oaub7B4pHOKKDLvL0+Y8mCagESgT+xye9LwQmJtiHq53XUD6iW0xCL0Mwg== X-Received: by 2002:a9d:5c7:: with SMTP id 65mr65205otd.360.1626110284882; Mon, 12 Jul 2021 10:18:04 -0700 (PDT) Received: from [192.168.0.41] (75-166-102-22.hlrn.qwest.net. [75.166.102.22]) by smtp.gmail.com with ESMTPSA id r3sm2587791ooh.37.2021.07.12.10.18.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 12 Jul 2021 10:18:04 -0700 (PDT) Subject: Re: [PATCH] Port GCC documentation to Sphinx To: =?UTF-8?Q?Martin_Li=c5=a1ka?= , Joseph Myers Cc: GCC Development , gcc-patches@gcc.gnu.org References: <1446990946.2994.192.camel@surprise> <1a22bc37-3d48-132f-a3d5-219471cd443c@suse.cz> <3a2a573b-5185-fff5-f9da-6e5e39953ad6@suse.cz> <8641dc55-5412-fbd7-bafd-13604311f5ad@suse.cz> <5ffe3e32-ece0-a1b4-1fcf-e35177fa80b5@suse.cz> <87489d9a-44e2-411c-3f3a-534d07e78b95@suse.cz> <0866a0ea-c846-ea5e-ac7a-d1c8f106cc45@suse.cz> <5bb9a10d-f3b9-f16a-7430-bbae2d4978e2@suse.cz> <2f60f602-5d88-7674-9620-2172748664c5@suse.cz> From: Martin Sebor Message-ID: <2afb9dc2-68d7-a1c6-49c2-e3d769e37ea0@gmail.com> Date: Mon, 12 Jul 2021 11:18:03 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <2f60f602-5d88-7674-9620-2172748664c5@suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_EU, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2021 17:18:06 -0000 On 6/29/21 4:09 AM, Martin Liška wrote: > On 6/28/21 5:33 PM, Joseph Myers wrote: >> Are formatted manuals (HTML, PDF, man, info) corresponding to this patch >> version also available for review? > > I've just uploaded them here: > https://splichal.eu/gccsphinx-final/ > > Martin > I think listing the -Wfoo and -Wno-foo (and analogously the -fbar and -fno-bar) options is an improvement over prior revisions but when the positive form is the default the text reads funny. For example: -fno-inline Do not expand any functions inline apart from those marked with the always_inline attribute. This is the default when not optimizing. Single functions can be exempted from inlining by marking them with the noinline attribute. -finline Default option value for -fno-inline. I.e., -finline is not what I would describe as a default value for -fno-inline. I would suggest to drop the option name from the text describing the default, and also replace value with setting (it's really not a value). It could be as simple as: -finline Default setting. Alternatively, to preserve the connection to the alternate setting: -finline Default setting; overrides -fno-inline. At some point we talked about also making attributes hyperlinks (like always_inline and noinline above) but I don't remember the conclusion. Are you planning to do that? (Would handling it as part of the transition be easier than doing it later?) Martin