From: Eric Botcazou <botcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: [Ada] Fix inaccurate bounds in debug info for vector array types
Date: Tue, 14 Sep 2021 11:12:34 +0200 [thread overview]
Message-ID: <8822831.CDJkKcVGEf@fomalhaut> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
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
[-- Attachment #2: p.diff --]
[-- Type: text/x-patch, Size: 659 bytes --]
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. */
reply other threads:[~2021-09-14 9:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8822831.CDJkKcVGEf@fomalhaut \
--to=botcazou@adacore.com \
--cc=gcc-patches@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).