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/30164] New: Restructure symbol domains
Date: Fri, 24 Feb 2023 17:27:35 +0000 [thread overview]
Message-ID: <bug-30164-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30164
Bug ID: 30164
Summary: Restructure symbol domains
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, symbol domains generally follow C.
That is, there is a domain for tags, some for non-C things
(Fortran stuff), a domain for labels, and then VAR_DOMAIN
for everything else -- types, functions, variables.
This leads to bad results, like bug #30158, where an
attempt to look up a function instead finds a namespace.
I think it would be better to drastically overhaul this code.
There should be many more domains, as many as we think
we'll need. Types, variables, and functions should all
be separate. Probably namespaces should also be their own thing.
Then, the symbol lookup functions should accept an enum flag
type of all the domains that should be searched.
This way, the C parser can implement its own semantics by
searching the relevant C domains -- but other language parsers
can do as they like.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-02-24 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 17:27 tromey at sourceware dot org [this message]
2023-03-01 13:30 ` [Bug symtab/30164] " tromey at sourceware dot org
2023-03-07 14:31 ` tromey at sourceware dot org
2023-09-14 16:28 ` tromey at sourceware dot org
2023-09-15 1:34 ` tromey at sourceware dot org
2023-11-19 16:55 ` tromey at sourceware dot org
2023-11-21 21:57 ` tromey at sourceware dot org
2024-01-28 23:44 ` cvs-commit at gcc dot gnu.org
2024-01-28 23: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-30164-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).