From: Bernhard Heckel <bernhard.heckel@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V4 5/6] Resolve dynamic target types of pointers.
Date: Tue, 08 Nov 2016 07:07:00 -0000 [thread overview]
Message-ID: <5821799A.6000708@intel.com> (raw)
In-Reply-To: <CAH=s-PPW_4uW0B92NtS2O7FjFYBfUwa=4exbp-N3AEpjpKfPuQ@mail.gmail.com>
On 20/10/2016 17:33, Yao Qi wrote:
> On Mon, Oct 17, 2016 at 1:18 PM, Bernhard Heckel
> <bernhard.heckel@intel.com> wrote:
>> I just looked again in the specification. It is not a bug.
>> FORTRAN specification (http://www.j3-fortran.org/doc/year/04/04-007.pdf)
>> mention this as "array pointer"
>>
> In "Glossary of technical terms", array pointer (5.1.2.5.3) : A pointer to an
> array, so it is a pointer, not an array.
>
> In your example,
>
> integer, pointer, dimension (:) :: intvlap
>
> It is a pointer in the debug information generated by icc. IMO, it is correct,
>
> - <1><78>: Abbrev Number: 4 (DW_TAG_pointer_type)
> - <79> DW_AT_type : <0x83>
> - <7d> DW_AT_associated : 5 byte block: 97 6 10 0 2e
> (DW_OP_push_object_address; DW_OP_deref; DW_OP_constu: 0; DW_OP_ne)
> - <1><83>: Abbrev Number: 5 (DW_TAG_array_type)
> - <84> DW_AT_ordering : 1 (column major)
> - <85> DW_AT_type : <0xa9>
> - <89> DW_AT_data_location: 2 byte block: 97 6
> (DW_OP_push_object_address; DW_OP_deref)
> - <2><8c>: Abbrev Number: 6 (DW_TAG_subrange_type)
> - <8d> DW_AT_byte_stride : 5 byte block: 97 10 38 22 6
> (DW_OP_push_object_address; DW_OP_constu: 56; DW_OP_plus; DW_OP_deref)
> - <93> DW_AT_upper_bound : 14 byte block: 97 10 40 22 6 97 10 30
> 22 6 22 10 1 1c (DW_OP_push_object_address; DW_OP_constu: 64;
> DW_OP_plus; DW_OP_deref; DW_OP_push_object_address; DW_OP_constu: 48;
> DW_OP_plus; DW_OP_deref; DW_OP_plus; DW_OP_constu: 1; DW_OP_minus)
> - <a2> DW_AT_lower_bound : 5 byte block: 97 10 40 22 6
> (DW_OP_push_object_address; DW_OP_constu: 64; DW_OP_plus; DW_OP_deref)
> - <2><a8>: Abbrev Number: 0
>
> however, it is an array in the debug information generated by gfortran,
> which is wrong.
>
> + <1><d1>: Abbrev Number: 9 (DW_TAG_array_type)
> + <d2> DW_AT_data_location: 2 byte block: 97 6
> (DW_OP_push_object_address; DW_OP_deref)
> + <d5> DW_AT_associated : 4 byte block: 97 6 30 2e
> (DW_OP_push_object_address; DW_OP_deref; DW_OP_lit0; DW_OP_ne)
> + <da> DW_AT_type : <0xca>
> + <de> DW_AT_sibling : <0xf5>
> + <2><e2>: Abbrev Number: 8 (DW_TAG_subrange_type)
> + <e3> DW_AT_lower_bound : 4 byte block: 97 23 20 6
> (DW_OP_push_object_address; DW_OP_plus_uconst: 32; DW_OP_deref)
> + <e8> DW_AT_upper_bound : 4 byte block: 97 23 28 6
> (DW_OP_push_object_address; DW_OP_plus_uconst: 40; DW_OP_deref)
> + <ed> DW_AT_byte_stride : 6 byte block: 97 23 18 6 34 1e
> (DW_OP_push_object_address; DW_OP_plus_uconst: 24; DW_OP_deref;
> DW_OP_lit4; DW_OP_mul)
> + <2><f4>: Abbrev Number: 0
>
Created a ticket
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78059
Can we agree to move forward with a "known fail" for Gfortran?
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2016-11-08 7:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 6:38 [PATCH V4 0/6] Fortran: Resolve " Bernhard Heckel
2016-09-07 6:38 ` [PATCH V4 5/6] Resolve dynamic " Bernhard Heckel
2016-09-07 14:24 ` Eli Zaretskii
2016-10-13 14:07 ` Yao Qi
2016-10-13 14:57 ` Bernhard Heckel
2016-10-17 10:32 ` Yao Qi
2016-10-17 11:25 ` Bernhard Heckel
2016-10-17 12:18 ` Bernhard Heckel
2016-10-20 11:52 ` Bernhard Heckel
2016-10-20 15:33 ` Yao Qi
2016-11-08 7:07 ` Bernhard Heckel [this message]
2016-11-08 11:26 ` Yao Qi
2016-11-08 12:27 ` Bernhard Heckel
2016-11-16 12:16 ` Bernhard Heckel
2016-11-21 15:03 ` Bernhard Heckel
2016-09-07 6:38 ` [PATCH V4 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-10-13 13:53 ` Yao Qi
2016-09-07 6:38 ` [PATCH V4 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-09-21 15:57 ` Yao Qi
2016-09-07 6:38 ` [PATCH V4 2/6] Fortran: Resolve dynamic properties of pointer types Bernhard Heckel
2016-10-05 8:44 ` Yao Qi
2016-10-05 9:36 ` Yao Qi
2016-10-05 10:07 ` Bernhard Heckel
2016-09-07 6:38 ` [PATCH V4 3/6] Typeprint: Resolve any dynamic target type of a pointer Bernhard Heckel
[not found] ` <861szvayzg.fsf@gmail.com>
2016-10-05 11:03 ` Bernhard Heckel
2016-10-13 13:41 ` Yao Qi
2016-09-07 6:38 ` [PATCH V4 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-10-13 14:08 ` Yao Qi
2016-09-14 12:55 ` [PING][PATCH V4 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-09-28 12:45 ` Bernhard Heckel
2016-10-05 6:03 ` [ping 2][PATCH " Bernhard Heckel
2016-09-21 9:49 ` [ping 2] [PATCH " Bernhard Heckel
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=5821799A.6000708@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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