From: Tom Tromey <tromey@adacore.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Paul Koning <paulkoning@comcast.net>,
Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Mark Pascal as case-insensitive
Date: Mon, 17 Nov 2025 08:03:10 -0700 [thread overview]
Message-ID: <877bvou2fl.fsf@tromey.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2511150214370.47194@angie.orcam.me.uk> (Maciej W. Rozycki's message of "Sat, 15 Nov 2025 02:30:20 +0000 (GMT)")
>> On Fri, 14 Nov 2025, Paul Koning wrote:
>> Is the purpose of that mechanism to allow individual symbols to be case
>> sensitive, or not? Neat, but where would that be used?
Maciej> Hmm, linking object modules coming from languages of the opposite symbol
Maciej> case sensitivity? We don't seem to have support for that in the tools or
Maciej> the object formats though and a DWARF tag is surely not enough for that.
I think currently the DWARF standard specifies DW_AT_identifier_case as
applying to the CU, not individual symbols.
However it seems to me that with LTO it would be better to relax this
and allow things like DW_AT_language on functions. That way gdb could
react correctly when stepping through code where cross-language inlining
has been done.
Tom
prev parent reply other threads:[~2025-11-17 15:28 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
2025-11-15 2:30 ` Maciej W. Rozycki
2025-11-17 15:03 ` Tom Tromey [this message]
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=877bvou2fl.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=paulkoning@comcast.net \
--cc=tdevries@suse.de \
/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