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] Restructure symbol domains
Date: Fri, 15 Sep 2023 01:34:19 +0000	[thread overview]
Message-ID: <bug-30164-4717-SrbvbLICbI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30164-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom Tromey from comment #2)
> I've been slowly working on this.
> 
> Lately I've been thinking that perhaps STRUCT_DOMAIN could
> be removed.  It's only needed for C and is the source of a
> hack in symbol_matches_domain.

On further reflection, I don't think this will work properly,
because in C it is fine to have a 'struct name' and a typedef
for 'name' that are different -- they really are separate
namespaces.

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

  parent reply	other threads:[~2023-09-15  1:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 17:27 [Bug symtab/30164] New: " tromey at sourceware dot org
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 [this message]
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-SrbvbLICbI@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).