public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: felix.willgerodt@intel.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] gdb, gdbserver: Add AMX registers.
Date: Mon, 27 Jun 2022 21:24:53 +0300	[thread overview]
Message-ID: <83y1xi6k22.fsf@gnu.org> (raw)
In-Reply-To: <fa8297a7-f9f5-8b41-e392-16a10c4a4cb1@palves.net> (message from Pedro Alves on Mon, 27 Jun 2022 19:16:33 +0100)

> Date: Mon, 27 Jun 2022 19:16:33 +0100
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
> 
> On 2022-05-11 12:41, Eli Zaretskii via Gdb-patches wrote:
> >> From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
> >> CC: "gdb-patches@sourceware.org" <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.

  reply	other threads:[~2022-06-27 18:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 12:12 [PATCH 0/4] Add AMX support Felix Willgerodt
2022-05-06 12:12 ` [PATCH 1/4] gdb: define int512 and uint512 as built-in types Felix Willgerodt
2022-05-06 12:19   ` Eli Zaretskii
2022-06-27 18:17   ` Pedro Alves
2022-05-06 12:12 ` [PATCH 2/4] gdb, gdbserver: Add AMX registers Felix Willgerodt
2022-05-06 12:25   ` Eli Zaretskii
2022-05-11  8:14     ` Willgerodt, Felix
2022-05-11 11:41       ` Eli Zaretskii
2022-06-27 18:16         ` Pedro Alves
2022-06-27 18:24           ` Eli Zaretskii [this message]
2022-06-27 19:15             ` Pedro Alves
2022-06-28 12:09               ` Eli Zaretskii
2022-06-28 13:35                 ` Pedro Alves
2022-05-06 16:17   ` John Baldwin
2022-05-09  7:04     ` Willgerodt, Felix
2022-05-09 16:31       ` John Baldwin
2022-06-27 18:12   ` Pedro Alves
2022-07-14 10:54     ` Willgerodt, Felix
2022-07-15 11:51       ` Willgerodt, Felix
2022-08-08  9:15     ` Willgerodt, Felix
2022-08-08 17:16       ` John Baldwin
2022-05-06 12:12 ` [PATCH 3/4] gdb, gdbserver: Allocate only a sane amount of buffer when fetching registers Felix Willgerodt
2022-05-06 16:08   ` John Baldwin
2022-05-09  7:04     ` Willgerodt, Felix
2022-06-27 18:30   ` Pedro Alves
2022-05-06 12:12 ` [PATCH 4/4] gdb: Clear tilecfg.start_row for any PC modification Felix Willgerodt
2022-06-27 18:55   ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y1xi6k22.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).