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
Subject: off-trunk gdb.fortran/dwarf-stride.exp no longer PASSes  [Re: [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic array support]
Date: Wed, 28 Oct 2015 15:30:00 -0000	[thread overview]
Message-ID: <20151027212831.GA3058@host1.jankratochvil.net> (raw)
In-Reply-To: <1435754532-17922-1-git-send-email-keven.boell@intel.com>

Hello,

this is not a regression for FSF GDB; but at least these Fedora versions
	gdb-7.8.2-39.fc21.x86_64
	gdb-7.9.1-17.fc22.x86_64
	gdb-7.10-29.fc24.x86_64
PASS the attached testcase
	p c40pt(1)^M
	$1 = '0-hello', ' ' <repeats 33 times>^M
	(gdb) PASS: gdb.fortran/dwarf-stride.exp: p c40pt(1)
	p c40pt(2)^M
	$2 = '1-hello', ' ' <repeats 33 times>^M
	(gdb) PASS: gdb.fortran/dwarf-stride.exp: p c40pt(2)
while current FSF trunk b80c3053162ec5533e120ee4e4ed30296d4c5fb2 FAILs on:
	p c40pt(1)^M
	$1 = '0-hello', ' ' <repeats 33 times>^M
	(gdb) PASS: gdb.fortran/dwarf-stride.exp: p c40pt(1)
	p c40pt(2)^M
	$2 = '\001\000\000\000\061-hello', ' ' <repeats 29 times>^M
	(gdb) FAIL: gdb.fortran/dwarf-stride.exp: p c40pt(2)

Curiously the Fedora GDB versions are based on:
	[PATCH 00/23] Fortran dynamic array support
	https://sourceware.org/ml/gdb-patches/2014-06/msg00108.html
	https://github.com/intel-gdb/vla/tree/vla-fortran
	commit 511bff520372ffc10fa2ff569c176bdf1e6e475d
	(although I cannot find that commit hash in that github repo now)

Couldn't the Intel patchset regress this testcase during its upstreaming?

I haven't yet tried to really fix/debug it.


Thanks,
Jan


  parent reply	other threads:[~2015-10-27 21:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 12:42 [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic array support Keven Boell
2015-07-01 12:42 ` [PATCH 2/2] fort_dyn_array: add basic test coverage Keven Boell
2015-07-21 18:19   ` Joel Brobecker
2015-08-05 13:41     ` Keven Boell
2015-07-01 12:42 ` [PATCH 1/2] fort_dyn_array: add basic fortran dyn array support Keven Boell
2015-07-21 18:05   ` Joel Brobecker
2015-08-05 13:41     ` Keven Boell
2015-08-05 13:47     ` Keven Boell
2015-08-05 20:23       ` Joel Brobecker
2015-08-06 11:42         ` keven.boell
2015-08-20 12:52           ` Joel Brobecker
2015-10-09 11:37             ` Keven Boell
2015-10-22  9:59               ` Joel Brobecker
2016-01-20 10:19               ` Yao Qi
2016-01-22  7:22                 ` Keven Boell
2016-01-22 12:40                   ` Joel Brobecker
2016-01-22 15:25                     ` Yao Qi
2016-01-26 12:34                       ` Joel Brobecker
     [not found]             ` <5613D0DC.3040908@linux.intel.com>
2015-10-22  9:59               ` Joel Brobecker
2015-10-28 15:30 ` Jan Kratochvil [this message]
2015-10-28 16:19   ` off-trunk gdb.fortran/dwarf-stride.exp no longer PASSes [Re: [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic array support] Jan Kratochvil
     [not found]     ` <20151028161907.GB4009@adacore.com>
2015-10-30 10:39       ` Jan Kratochvil
2015-11-04 21:48         ` Joel Brobecker
2015-11-04 22:08           ` Jan Kratochvil
2015-11-05  7:31             ` Keven Boell
2015-11-05  8:22               ` Jan Kratochvil
2015-11-05 16:05                 ` Keven Boell

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=20151027212831.GA3058@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keven.boell@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