[Bug symtab/30661] [gdb/symtab] main symbol language lookup causes symtab expansion

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d06730bc0205f7c35bfccf057ef0ef83a12206d6

commit d06730bc0205f7c35bfccf057ef0ef83a12206d6
Author: Tom de Vries <tdevries@suse.de>
Date:   Sat Aug 5 17:57:13 2023 +0200

    [gdb/symtab] Find main language without symtab expansion

    When loading an executable using "file a.out", the language is set
according
    to a.out, which can involve looking up the language of symbol "main", which
    will cause the symtab expansion for the containing CU.

    Expansion of lto debug info can be slow, so in commit d3214198119 ("[gdb]
Use
    partial symbol table to find language for main") a feature was added to
avoid
    the symtab expansion.

    This feature stopped working after commit 7f4307436fd ("Fix "start" for D,
    Rust, etc").

    [ The commit addresses problems related to command start, which requires
finding
    the main function:
    - for language D, "main" was found instead of "D main", and
    - for Rust, the correct function was found, but attributed the wrong name
      (not fully qualified). ]

    Reimplement the feature by adding
    cooked_index_functions::lookup_global_symbol_language.

    Tested on x86_64-linux.

    PR symtab/30661
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30661

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