public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109006] [13 Regression] Python Exception <class 'gdb.error'>: There is no member or method named m_vecdata. since r13-6332
Date: Sat, 04 Mar 2023 10:24:41 +0000 [thread overview]
Message-ID: <bug-109006-4-wUtV2awJM2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109006-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109006
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:4ee2f419fe42222dbb21dfb0622cc7c0e46a2261
commit r13-6478-g4ee2f419fe42222dbb21dfb0622cc7c0e46a2261
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat Mar 4 11:24:04 2023 +0100
Remove remaining traces of m_vecdata from comments [PR109006]
The following patch adjusts remaining references to the removed m_vecdata
array from vec.h in various comments.
2023-03-04 Jakub Jelinek <jakub@redhat.com>
PR middle-end/109006
* vec.cc (test_auto_alias): Adjust comment for removal of
m_vecdata.
* read-rtl-function.cc (function_reader::parse_block): Likewise.
* gdbhooks.py: Likewise.
next prev parent reply other threads:[~2023-03-04 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:52 [Bug middle-end/109006] New: " jakub at gcc dot gnu.org
2023-03-03 11:52 ` [Bug middle-end/109006] " jakub at gcc dot gnu.org
2023-03-03 12:01 ` jakub at gcc dot gnu.org
2023-03-03 16:53 ` cvs-commit at gcc dot gnu.org
2023-03-03 18:15 ` cvs-commit at gcc dot gnu.org
2023-03-04 10:24 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-04 10:27 ` jakub 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-109006-4-wUtV2awJM2@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).