Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: Tom Tromey <tromey@adacore.com>
Cc: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Mark Pascal as case-insensitive
Date: Fri, 14 Nov 2025 17:02:45 -0500	[thread overview]
Message-ID: <87AA3F28-5E27-49F2-A2C6-D14BA082A830@comcast.net> (raw)
In-Reply-To: <87ecq0whxx.fsf@tromey.com>



> On Nov 14, 2025, at 2:08 PM, Tom Tromey <tromey@adacore.com> wrote:
> 
> Tom> FWIW, I just found DW_AT_identifier_case:
> Tom> ...
> Tom>  <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
> Tom>     <c>   DW_AT_name        :
> Tom>     ../../../../src/gdb/testsuite/gdb.pascal/hello.pas
> Tom>     <3f>   DW_AT_producer    : Free Pascal 3.2.2 2025/09/10
> Tom>     <5c>   DW_AT_comp_dir    :
> Tom>     /data/vries/gdb/leap-16-0/build/gdb/testsuite/
> Tom>     <8b>   DW_AT_language    : 9        (ANSI Pascal)
> Tom>     <8c>   DW_AT_identifier_case: 3     (case_insensitive)
> Tom>     <8d>   DW_AT_stmt_list   : 0
> Tom>     <91>   DW_AT_low_pc      : 0x401090
> Tom>     <99>   DW_AT_high_pc     : 0x401150
> Tom> ...
> Tom> which enables a finer granularity.  We currently don't support this,
> Tom> but I'm not sure if that's a relevant feature.
> 
> I also didn't know about this.
> 
> We could probably handle this in gdb, maybe by enhancing the
> canonicalization step, though other approaches are possible.
> 
> Tom

Is the purpose of that mechanism to allow individual symbols to be case sensitive, or not?  Neat, but where would that be used?

	paul


  reply	other threads:[~2025-11-14 22:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:28 Tom Tromey
2025-11-14 11:41 ` Tom de Vries
2025-11-14 12:59   ` Tom de Vries
2025-11-14 19:08     ` Tom Tromey
2025-11-14 22:02       ` Paul Koning [this message]
2025-11-15  2:30         ` Maciej W. Rozycki
2025-11-17 15:03           ` Tom Tromey

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=87AA3F28-5E27-49F2-A2C6-D14BA082A830@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tromey@adacore.com \
    /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