From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id DPN6C9cBumKtwwcAWB0awg (envelope-from ) for ; Mon, 27 Jun 2022 15:15:35 -0400 Received: by simark.ca (Postfix, from userid 112) id 1DAF21E22B; Mon, 27 Jun 2022 15:15:35 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, NICE_REPLY_A,RDNS_DYNAMIC autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (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 simark.ca (Postfix) with ESMTPS id 7AB641E15C for ; Mon, 27 Jun 2022 15:15:34 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id DCA27383DB91 for ; Mon, 27 Jun 2022 19:15:32 +0000 (GMT) Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) by sourceware.org (Postfix) with ESMTPS id D89FC38582BE for ; Mon, 27 Jun 2022 19:15:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D89FC38582BE Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f47.google.com with SMTP id s1so14388934wra.9 for ; Mon, 27 Jun 2022 12:15:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=6PjPA7C9frpgGlEbGLCjmJD7qUgG6c0Njfxhv6ug/XE=; b=oG6OKrQl6c01uZnQGXomNCuSL2Oz+hVdzmi6f7zE7kgQagIM0NzWrRjMKtiME54Jbr oMxZKA23BjAKZZelcjb2MCtKHJgWj2//X/AFPgU9GnXJ+t582+l1DR81u7RiUKb7JbNL crF3CGiCtpWDYxvHxBZmvNwe66O4HBJPZ7dB1jdVsWMZpFV7GW9KSJWXC+PLwjKZrMuR Z+LjLLdFBkhfDwmtq/SO23rWjkNtVA9eBUaFCyAiQweta4/4q8or2Q6Yfa2mmkfLb0jf vARhtpX6o22rBBDsszmM/2x5aITn/bNoT/A64rUqmXUBlsEgs2T67ZECdgP0KOy5OBO+ Sm3Q== X-Gm-Message-State: AJIora/DhRcQeY0D/QJoBH7JEzi826ixmgTzraw04fgt1SSrBSBYK261 ryu5huk9KbtWH0ykvLqpVr8= X-Google-Smtp-Source: AGRyM1sLzeXrgJaQ9YY2OSo7a2sStXViAxoJG3J0nNEEocPjDOsogwS+6YIRF4EqYDZ+YSRvFcksuw== X-Received: by 2002:a5d:5261:0:b0:21b:8740:382b with SMTP id l1-20020a5d5261000000b0021b8740382bmr13135159wrc.143.1656357319642; Mon, 27 Jun 2022 12:15:19 -0700 (PDT) Received: from ?IPV6:2001:8a0:f924:2600:5b14:8ad0:780f:bdda? ([2001:8a0:f924:2600:5b14:8ad0:780f:bdda]) by smtp.gmail.com with ESMTPSA id u6-20020a5d5146000000b0020fcc655e4asm11494164wrt.5.2022.06.27.12.15.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Jun 2022 12:15:18 -0700 (PDT) Message-ID: Date: Mon, 27 Jun 2022 20:15:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH 2/4] gdb, gdbserver: Add AMX registers. Content-Language: en-US To: Eli Zaretskii References: <20220506121226.137608-1-felix.willgerodt@intel.com> <20220506121226.137608-3-felix.willgerodt@intel.com> <834k2226ht.fsf@gnu.org> <834k1ws3d3.fsf@gnu.org> <83y1xi6k22.fsf@gnu.org> From: Pedro Alves In-Reply-To: <83y1xi6k22.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2022-06-27 19:24, Eli Zaretskii wrote: >> Date: Mon, 27 Jun 2022 19:16:33 +0100 >> Cc: gdb-patches@sourceware.org >> From: Pedro Alves >> >> On 2022-05-11 12:41, Eli Zaretskii via Gdb-patches wrote: >>>> From: "Willgerodt, Felix" >>>> CC: "gdb-patches@sourceware.org" >>>> Date: Wed, 11 May 2022 08:14:26 +0000 >>>> >>>>> Please make @cindex entries start with a lower-case letter. >>>>> Otherwise, the index could be sorted differently in different locales. >>>>> >>>> >>>> I tried it, it just doesn't look right to me if I don't use capital letters. >>>> (Writing "advanced Matrix Extensions" or "advanced matrix extensions".) >>>> >>>> There are many index entries starting with capital letters, e.g. AArch64, >>>> ARM or Ada. I see that Intel MPX is added as "Intel Memory Protection >>>> Extensions (MPX)". Features of other vendors/architectures seem to >>>> have similar formatting, like "AArch64 SVE" or "AArch64 Memory >>>> Tagging Extension". Can I use the same formatting for AMX? >>>> E.g. "Intel Advanced Memory Extensions (AMX)". >>> >>> If you start with "Intel" (or another non-word), yes. >> >> Hi Eli, >> >> I'm curious about this. What is different between "Intel" and "Advanced" here, >> wrt to locale, since they are both upper case? > > The locale doesn't matter, but people do. "Intel" is not a word, so > it doesn't really matter in what place in the sort order it winds up, > as long as we always spell it with the capital "I". But if "Advanced" > is in one place and "advanced" is in a very different place, people > may have trouble finding one or the other, if they look up stuff in > alphabetical order. > Given the manual is written in US English, I wonder why we let locale influence sorting order. I mean, shouldn't we be forcing locale to LANC=C or some such when generating the manual, to be sure the sections are always sorted the same way? (At least the html manual sorts the concept index ignoring case for me, and I see the same in the docs copy in the gdb website, so I assume that's the order we want.)