public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/103315] Gfortran DW_AT_Rank expression not emitting correct rank value. Date: Thu, 18 Nov 2021 14:26:26 +0000 [thread overview] Message-ID: <bug-103315-4-837LL7yFwo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103315-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103315 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Would DW_OP_deref_size 1 instead of DW_OP_deref fix this? dtype.rank field is I think unsigned char. I.e.: 2021-11-18 Jakub Jelinek <jakub@redhat.com> PR debug/103315 * trans-types.c (gfc_get_array_descr_info): Use DW_OP_deref_size 1 instead of DW_OP_deref for DW_AT_rank. --- gcc/fortran/trans-types.c.jj 2021-11-12 15:54:21.000000000 +0100 +++ gcc/fortran/trans-types.c 2021-11-18 15:13:45.131281198 +0100 @@ -3459,8 +3459,8 @@ gfc_get_array_descr_info (const_tree typ if (!integer_zerop (dtype_off)) t = fold_build_pointer_plus (t, rank_off); - t = build1 (NOP_EXPR, build_pointer_type (gfc_array_index_type), t); - t = build1 (INDIRECT_REF, gfc_array_index_type, t); + t = build1 (NOP_EXPR, build_pointer_type (TREE_TYPE (field)), t); + t = build1 (INDIRECT_REF, TREE_TYPE (field), t); info->rank = t; t = build0 (PLACEHOLDER_EXPR, TREE_TYPE (dim_off)); t = size_binop (MULT_EXPR, t, dim_size);
next prev parent reply other threads:[~2021-11-18 14:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 13:53 [Bug debug/103315] New: " rupesh.potharla at amd dot com 2021-11-18 14:26 ` jakub at gcc dot gnu.org [this message] 2021-11-21 20:08 ` [Bug debug/103315] " cvs-commit at gcc dot gnu.org 2021-11-29 8:50 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:21 ` [Bug fortran/103315] " cvs-commit at gcc dot gnu.org 2022-05-11 6:23 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` 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-103315-4-837LL7yFwo@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: 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).