public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30115] New: Investigate use of case-folding in cooked-index
Date: Sun, 12 Feb 2023 16:17:26 +0000	[thread overview]
Message-ID: <bug-30115-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30115

            Bug ID: 30115
           Summary: Investigate use of case-folding in cooked-index
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

Right now the cooked index does case-insensitive comparisons.
But is this really needed?

I think there are a few case-insensitive languages in gdb.

GNAT already case-folds all symbol names.  In fact, due to the
way GNAT encodes non-ASCII characters, case-folding in the index
might mean that you could construct a situation where symbol
lookup finds the wrong thing.

I haven't looked to see what Pascal, Modula-2, or Fortran do.

However, for those, one option might be to do the folding as
a canonicalization step.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-02-12 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 16:17 tromey at sourceware dot org [this message]
2023-02-12 16:17 ` [Bug symtab/30115] " tromey at sourceware dot org
2023-08-31 13:45 ` tromey at sourceware dot org

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=bug-30115-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).