From: Keven Boell <keven.boell@linux.intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Keven Boell <keven.boell@intel.com>
Cc: gdb-patches@sourceware.org, sanimir.agovic@intel.com
Subject: Re: [V2 09/23] vla: changed string length semantic.
Date: Mon, 21 Jul 2014 13:23:00 -0000 [thread overview]
Message-ID: <53CCCE51.1030603@linux.intel.com> (raw)
In-Reply-To: <20140718151945.GA11512@host2.jankratochvil.net>
On 18.07.2014 17:19, Jan Kratochvil wrote:
> Hi Keven,
>
> the regression discussed in
> Re: [V2 00/23] Fortran dynamic array support
> https://sourceware.org/ml/gdb-patches/2014-07/msg00278.html
>
> is IMO here:
>
> On Fri, 11 Jul 2014 11:21:21 +0200, Keven Boell wrote:
>> @@ -14590,8 +14680,26 @@ attr_to_dynamic_prop (const struct attribute *attr, struct die_info *die,
>> baton = obstack_alloc (obstack, sizeof (*baton));
>> baton->referenced_type = die_type (target_die, target_cu);
>> baton->locexpr.per_cu = cu->per_cu;
>> - baton->locexpr.size = DW_BLOCK (target_attr)->size;
>> - baton->locexpr.data = DW_BLOCK (target_attr)->data;
>> +
>> + if (additional_data != NULL && additional_data_size > 0)
>> + {
>> + gdb_byte *data;
>> +
>> + data = obstack_alloc (&cu->objfile->objfile_obstack,
>> + DW_BLOCK (attr)->size + additional_data_size);
>> + memcpy (data, DW_BLOCK (attr)->data, DW_BLOCK (attr)->size);
>> + memcpy (data + DW_BLOCK (attr)->size,
>> + additional_data, additional_data_size);
>> +
>> + baton->locexpr.data = data;
>> + baton->locexpr.size = DW_BLOCK (attr)->size + additional_data_size;
>> + }
>> + else
>> + {
>> + baton->locexpr.data = DW_BLOCK (attr)->data;
>> + baton->locexpr.size = DW_BLOCK (attr)->size;
>> + }
>> +
>> prop->data.baton = baton;
>> prop->kind = PROP_LOCEXPR;
>> gdb_assert (prop->data.baton != NULL);
>
> it was correctly using 'target_attr' but now it uses 'attr' instead.
>
> The gdb.ada/ regression gets fixed for me by the attached patch.
>
Thanks for your investigation. Seems like I did a copy and paste error here, you are
right, target_attr is the right variable to use in this case.
I pushed the updated series to Github: https://github.com/intel-gdb/vla/tree/vla-fortran
>
> Jan
>
Thanks,
Keven
next prev parent reply other threads:[~2014-07-21 8:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 9:21 [V2 00/23] Fortran dynamic array support Keven Boell
2014-07-11 9:21 ` [V2 05/23] vla: make field selection work with vla Keven Boell
2014-07-11 9:21 ` [V2 16/23] test: correct ptype of dynamic arrays in Fortran Keven Boell
2014-07-11 9:21 ` [V2 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode Keven Boell
2014-07-11 9:21 ` [V2 08/23] vla: get dynamic array corner cases to work Keven Boell
2014-07-11 9:21 ` [V2 09/23] vla: changed string length semantic Keven Boell
2014-07-18 15:38 ` Jan Kratochvil
2014-07-21 13:23 ` Keven Boell [this message]
2014-07-21 19:54 ` Jan Kratochvil
2014-07-22 15:27 ` Keven Boell
2014-07-11 9:21 ` [V2 21/23] test: basic MI test for the dynamic array support Keven Boell
2014-07-11 9:21 ` [V2 19/23] test: accessing dynamic array history values Keven Boell
2014-07-11 9:21 ` [V2 12/23] vla: add NEWS entry for dynamic array support Keven Boell
2014-07-11 9:58 ` Eli Zaretskii
2014-07-11 9:22 ` [V2 18/23] test: dynamic arrays passed to functions Keven Boell
2014-07-11 9:22 ` [V2 13/23] test: basic tests for dynamic array evaluations in Fortran Keven Boell
2014-07-11 9:22 ` [V2 07/23] vla: use value constructor instead of raw-buffer manipulation Keven Boell
2014-07-11 9:22 ` [V2 20/23] test: dynamic string evaluations Keven Boell
2014-07-11 9:22 ` [V2 17/23] test: evaluating allocation/association status Keven Boell
2014-07-11 9:22 ` [V2 11/23] vla: add stride support to fortran arrays Keven Boell
2014-07-11 9:22 ` [V2 22/23] test: test sizeof for dynamic " Keven Boell
2014-07-11 9:22 ` [V2 15/23] test: dynamic arrays passed to subroutines Keven Boell
2014-08-01 20:11 ` Jan Kratochvil
2014-08-07 6:58 ` Keven Boell
2014-08-12 6:56 ` Keven Boell
2014-07-11 9:22 ` [V2 23/23] test: stride support for dynamic arrays Keven Boell
2014-07-11 9:22 ` [V2 03/23] vla: introduce allocated/associated flags Keven Boell
2014-07-11 9:22 ` [V2 14/23] test: evaluate dynamic arrays using Fortran primitives Keven Boell
2014-07-11 9:22 ` [V2 02/23] dwarf: add DW_AT_data_location support Keven Boell
2014-07-11 9:22 ` [V2 04/23] vla: make dynamic fortran arrays functional Keven Boell
2014-07-11 9:22 ` [V2 06/23] vla: reconstruct value to compute bounds of target type Keven Boell
2014-07-11 9:28 ` [V2 10/23] vla: get Fortran dynamic strings working Keven Boell
2014-07-11 16:23 ` [V2 00/23] Fortran dynamic array support Jan Kratochvil
2014-07-16 16:19 ` Keven Boell
2014-07-16 16:33 ` Jan Kratochvil
2014-07-18 12:33 ` Keven Boell
2014-07-18 15:19 ` Jan Kratochvil
2014-07-29 19:35 ` Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support] Jan Kratochvil
2014-07-29 20:51 ` Jan Kratochvil
2014-08-01 7:20 ` Keven Boell
2014-08-01 7:22 ` Jan Kratochvil
2014-08-01 21:02 ` [patch 1/2] " Jan Kratochvil
2014-08-12 6:56 ` Keven Boell
2014-08-12 21:55 ` Jan Kratochvil
2014-08-14 20:03 ` Jan Kratochvil
2014-08-20 14:09 ` Keven Boell
2014-08-20 18:24 ` Jan Kratochvil
2014-08-21 7:27 ` Keven Boell
2014-08-21 14:29 ` Jan Kratochvil
2014-08-22 7:20 ` Jan Kratochvil
2014-08-01 21:05 ` [patch 2/2] " Jan Kratochvil
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=53CCCE51.1030603@linux.intel.com \
--to=keven.boell@linux.intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keven.boell@intel.com \
--cc=sanimir.agovic@intel.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