From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 791C23858D37; Fri,  3 Mar 2023 12:01:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 791C23858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677844911;
	bh=SnCuPafQH6++tVokLu22IOPOhr+viFoF/8PH3AYl9/Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mO13v7vuU+yDuXjhiSauHr1ZAxik5yu/iEI4u7yizwIABGBfno3T/HwiA+7TqucnG
	 JOznaD4I2hFmRV4NEdAGmBJWUDImS2W6tdME61hzq0ofS+h+zQt5JJ/7ijP58sIKhu
	 kdZsfnNjKTQ+cA+A/eHJbZmTb3sUpODLPbA1U8Es=
From: "jakub 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: Fri, 03 Mar 2023 12:01:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109006-4-hsTuVa4kTW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109006-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109006-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109006

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As for the non-*.py comments, perhaps:
2023-03-03  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.

--- gcc/vec.cc.jj       2023-02-27 09:41:30.910265623 +0100
+++ gcc/vec.cc  2023-03-03 13:00:01.941663049 +0100
@@ -568,7 +568,7 @@ test_auto_delete_vec ()
   ASSERT_EQ (dtor_count, 2);
 }

-/* Verify accesses to m_vecdata are done indirectly.  */
+/* Verify accesses to vector elements are done indirectly.  */

 static void
 test_auto_alias ()
--- gcc/read-rtl-function.cc.jj 2023-01-02 09:32:54.001828467 +0100
+++ gcc/read-rtl-function.cc    2023-03-03 12:59:15.941340372 +0100
@@ -622,10 +622,11 @@ function_reader::parse_block ()

      These can get out-of-sync when basic blocks are optimized away.
      They get back in sync by "compact_blocks".
-     We reconstruct cfun->cfg->x_basic_block_info->m_vecdata with NULL
-     values in it for any missing basic blocks, so that (a) =3D=3D (b) for
-     all of the blocks we create.  The doubly-linked list of basic
-     blocks (next_bb/prev_bb) skips over these "holes".  */
+     We reconstruct cfun->cfg->x_basic_block_info->address () pointed
+     vector elements with NULL values in it for any missing basic blocks,
+     so that (a) =3D=3D (b) for all of the blocks we create.  The
+     doubly-linked list of basic blocks (next_bb/prev_bb) skips over
+     these "holes".  */

   if (m_highest_bb_idx < bb_idx)
     m_highest_bb_idx =3D bb_idx;=