public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/31295] Slow symbol lookup due to missing DW_AT_const_value attribute
Date: Fri, 26 Jan 2024 05:22:44 +0000	[thread overview]
Message-ID: <bug-31295-4717-6FPvFMLq5Y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31295-4717@http.sourceware.org/bugzilla/>

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
I build the gdb-14.1-release tag.  Then I tried constructing a 2-CU example out
of comment 0.  But I don't manage to reproduce the described behaviour, I see
only one CU being expanded.  I tried compiling with both gcc-12 and clang
15.0.7:
...
$ cat test.h
#include <cstddef>

class wxString
{
public:
  static const size_t npos;
};
$ cat test.cpp
#include "test.h"

const size_t wxString::npos = (size_t) -1;

extern int foo (void);

int
main (void)
{
  return foo ();
}
$ cat test-2.cpp
#include "test.h"

extern int foo (void);

int
foo (void)
{
  return wxString::npos + 1;
}
$ g++-12 test.cpp test-2.cpp -g
$ gdb -q -batch a.out -ex "set trace-commands on" -ex "maint info symtab" -ex
"ptype wxString" -ex "maint info symtab"
+maint info symtab
+ptype wxString
type = class wxString {
  public:
    static const size_t npos;
}
+maint info symtab
{ objfile /data/vries/gdb/a.out ((struct objfile *) 0x48beb90)
  { ((struct compunit_symtab *) 0x48b62a0)
    debugformat DWARF 4
    producer GNU C++17 12.3.0 -mtune=generic -march=x86-64 -g
    name test.cpp
    dirname /home/vries/gdb
    blockvector ((struct blockvector *) 0x48f82a0)
    user ((struct compunit_symtab *) (null))
        { symtab test.cpp ((struct symtab *) 0x48b6320)
          fullname (null)
          linetable ((struct linetable *) 0x48f82d0)
        }
        { symtab /usr/include/c++/12/x86_64-suse-linux/bits/c++config.h
((struct symtab *) 0x48b6360)
          fullname (null)
          linetable ((struct linetable *) 0x0)
        }
        { symtab /usr/lib64/gcc/x86_64-suse-linux/12/include/stddef.h ((struct
symtab *) 0x48b63a0)
          fullname (null)
          linetable ((struct linetable *) 0x0)
        }
        { symtab /usr/include/c++/12/cstddef ((struct symtab *) 0x48b63e0)
          fullname (null)
          linetable ((struct linetable *) 0x0)
        }
        { symtab test.h ((struct symtab *) 0x48b6420)
          fullname (null)
          linetable ((struct linetable *) 0x0)
        }
  }
}
...

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

  parent reply	other threads:[~2024-01-26  5:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 16:24 [Bug symtab/31295] New: " dmitry.neverov at jetbrains dot com
2024-01-25 18:58 ` [Bug symtab/31295] " dmitry.neverov at jetbrains dot com
2024-01-26  3:26 ` tromey at sourceware dot org
2024-01-26  5:22 ` vries at gcc dot gnu.org [this message]
2024-01-26  9:31 ` dmitry.neverov at jetbrains dot com
2024-01-26 11:41 ` ssbssa at sourceware dot org
2024-01-26 12:28 ` vries at gcc dot gnu.org
2024-01-26 13:28 ` dmitry.neverov at jetbrains dot com
2024-01-26 15:43 ` vries at gcc dot gnu.org
2024-01-27 11:09 ` sam at gentoo dot org
2024-01-28 20:23 ` tromey at sourceware dot org
2024-01-29  1:10 ` tromey at sourceware dot org
2024-02-11 17:52 ` tromey at sourceware dot org
2024-02-11 20:37 ` tromey at sourceware dot org
2024-02-11 21:15 ` tromey at sourceware dot org
2024-02-12 15:44 ` vries at gcc dot gnu.org
2024-02-12 20:28 ` tromey at sourceware dot org
2024-02-16  2:32 ` 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-31295-4717-6FPvFMLq5Y@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).