Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Keven Boell <keven.boell@intel.com>
Cc: gdb-patches@sourceware.org, sanimir.agovic@intel.com
Subject: Re: [V2 15/23] test: dynamic arrays passed to subroutines.
Date: Fri, 01 Aug 2014 20:11:00 -0000	[thread overview]
Message-ID: <20140801201133.GA24508@host2.jankratochvil.net> (raw)
In-Reply-To: <1405070495-6948-16-git-send-email-keven.boell@intel.com>

On Fri, 11 Jul 2014 11:21:27 +0200, Keven Boell wrote:
> +gdb_test "finish" \
> +  ".*foo\\\(sub_arr1\\\(5:10, 5:10\\\), sub_arr2\\\(10:15,10:15,10:15\\\)\\\)" \
> +  "finish function"

This testcase FAILs for 32-bit targets (FAILs on both x86_64-m32 and on i686).

finish^M
Run till exit from #0  foo (array1=..., array2=...) at gdb/testsuite/gdb.fortran/vla-sub.f90:31^M
0x08048aa5 in vla_sub () at gdb/testsuite/gdb.fortran/vla-sub.f90:72^M
72        call foo(sub_arr1, sub_arr2)^M
(gdb) FAIL: gdb.fortran/vla-value-sub-finish.exp: finish function
 8048aa0:       e8 e9 fb ff ff          call   804868e <foo_>
 8048aa5:       83 c4 08                add    $0x8,%esp
/home/jkratoch/redhat/gdb-vla-intel-noasan/gdb/testsuite/./gdb.fortran/vla-sub.f90:73

finish^M
Run till exit from #0  foo (array1=..., array2=...) at gdb/testsuite/gdb.fortran/vla-sub.f90:31^M
vla_sub () at gdb/testsuite/gdb.fortran/vla-sub.f90:73^M
73        call foo(sub_arr1(5:10, 5:10), sub_arr2(10:15,10:15,10:15))^M
(gdb) PASS: gdb.fortran/vla-value-sub-finish.exp: finish function
  400d34:       e8 23 fb ff ff          callq  40085c <foo_>
/home/jkratoch/redhat/gdb-vla-intel-noasan/gdb/testsuite/./gdb.fortran/vla-sub.f90:73

It is understandable, "finish" command sometimes ends up on the caller source
line and sometimes on the next source line after caller, depending on the arch.

At least this way it happens on:
	gcc-4.9.1-2.fc21.1.x86_64


Thanks,
Jan


  reply	other threads:[~2014-08-01 20:11 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 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode 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 05/23] vla: make field selection work with vla 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:21 ` [V2 19/23] test: accessing dynamic array history values 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
2014-07-21 19:54       ` Jan Kratochvil
2014-07-22 15:27         ` 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 21/23] test: basic MI test for the dynamic array support 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 22/23] test: test sizeof for dynamic fortran arrays 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 [this message]
2014-08-07  6:58     ` Keven Boell
2014-08-12  6:56       ` 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 17/23] test: evaluating allocation/association status 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 18/23] test: dynamic arrays passed to functions 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 06/23] vla: reconstruct value to compute bounds of target type Keven Boell
2014-07-11  9:22 ` [V2 04/23] vla: make dynamic fortran arrays functional 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 14/23] test: evaluate dynamic arrays using Fortran primitives 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=20140801201133.GA24508@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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