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: Fri, 30 Dec 2022 12:55:27 +0000 [thread overview] Message-ID: <bug-29343-4717-qGI2t9Qctc@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 #10 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=d8f52a9a9ccbf7411cf4ae487d2756826f5d0bd5 commit d8f52a9a9ccbf7411cf4ae487d2756826f5d0bd5 Author: Tom de Vries <tdevries@suse.de> Date: Fri Dec 30 13:55:22 2022 +0100 [gdb/symtab] Make comp_unit_head.length private Make comp_unit_head.length private, to enforce using accessor functions. Replace accessor function get_length with get_length_with_initial and get_length_without_initial, to make it explicit which variant we're using. Tested on x86_64-linux. PR symtab/29343 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.
prev parent reply other threads:[~2022-12-30 12:55 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 2022-12-26 21:03 ` tromey at sourceware dot org 2022-12-30 12:55 ` cvs-commit at gcc dot gnu.org [this message]
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-qGI2t9Qctc@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: linkBe 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).