[Ada] Fix inaccurate bounds in debug info for vector array types

Message ID 8822831.CDJkKcVGEf@fomalhaut
State New
Headers show
Series
  • [Ada] Fix inaccurate bounds in debug info for vector array types
Related show

Commit Message

Eric Botcazou Sept. 14, 2021, 9:12 a.m.
They should not be 0-based, unless the array type itself is.

Tested on x86-64/Linux, applied on the mainline, 11 and 10 branches.


2021-09-14  Eric Botcazou  <ebotcazou@adacore.com>

	* gcc-interface/decl.c (gnat_to_gnu_entity): For vector types, make
	the representative array the debug type.

-- 
Eric Botcazou

Patch

diff --git a/decl.c b/decl.c
index f7394b60..ebb33c97 100644
--- a/decl.c
+++ b/decl.c
@@ -4744,6 +4744,14 @@  gnat_to_gnu_entity (Entity_Id gnat_entity, tree gnu_expr, bool definition)
       else
 	gnu_decl = create_type_decl (gnu_entity_name, gnu_type, artificial_p,
 				     debug_info_p, gnat_entity);
+
+      /* For vector types, make the representative array the debug type.  */
+      if (VECTOR_TYPE_P (gnu_type))
+	{
+	  tree rep = TYPE_REPRESENTATIVE_ARRAY (gnu_type);
+	  TYPE_NAME (rep) = DECL_NAME (gnu_decl);
+	  SET_TYPE_DEBUG_TYPE (gnu_type, rep);
+	}
     }
 
   /* Otherwise, for a type reusing an existing DECL, back-annotate values.  */