public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29343] [gdb/symtab] c++-ify comp_unit_head
Date: Mon, 26 Dec 2022 20:59:23 +0000	[thread overview]
Message-ID: <bug-29343-4717-Uclhi9zNiv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29343-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

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

commit 4d78ce772370fa48b9a749f81205076f26eba846
Author: Tom Tromey <tom@tromey.com>
Date:   Fri Jul 15 19:05:29 2022 -0600

    Add initializers to comp_unit_head

    PR symtab/29343 points out that it would be beneficial if
    comp_unit_head had a constructor and used initializers.  This patch
    implements this.  I'm unsure if this is sufficient to close the bug,
    but at least it's a step.

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

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

  parent reply	other threads:[~2022-12-26 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09  8:24 [Bug symtab/29343] New: [gdb/symtab] per_cu->length set without initial_length_size vries at gcc dot gnu.org
2022-07-09  8:24 ` [Bug symtab/29343] " vries at gcc dot gnu.org
2022-07-09  8:34 ` vries at gcc dot gnu.org
2022-07-09  9:17 ` vries at gcc dot gnu.org
2022-07-11  9:40 ` vries at gcc dot gnu.org
2022-07-13  7:41 ` vries at gcc dot gnu.org
2022-07-13  7:42 ` [Bug symtab/29343] [gdb/symtab] c++-ify comp_unit_head vries at gcc dot gnu.org
2022-12-24 22:45 ` tromey at sourceware dot org
2022-12-25  8:25 ` vries at gcc dot gnu.org
2022-12-26 20:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-26 21:03 ` tromey at sourceware dot org
2022-12-30 12:55 ` cvs-commit at gcc dot gnu.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-29343-4717-Uclhi9zNiv@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).