From: Bernhard Heckel <bernhard.heckel@intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "Weinmann, Christoph T" <christoph.t.weinmann@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [V4 00/21] Fortran dynamic array support
Date: Wed, 14 Sep 2016 07:24:00 -0000 [thread overview]
Message-ID: <57D8FB1F.1040000@intel.com> (raw)
In-Reply-To: <20160912210453.GA32414@host1.jankratochvil.net>
On 12/09/2016 23:04, Jan Kratochvil wrote:
> On Wed, 07 Sep 2016 12:29:06 +0200, Bernhard Heckel wrote:
>> I just recreated my two user branches.
> I see a regression against former Intel VLA patchset for the attached testcase.
>
> gdb_test "p c40pt(2)" " = '1-hello.*"
> 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)
>
>
> Thanks,
> Jan
Hi Jan,
I tested with GCC 4.8.3 and IFORT 17.0.0. Both passes.
With Fedora24, GCC 6.1.1 I see the same results as you. Investigation is
showing that
GCC 6.1.1 doesn't provide the stride information (DWARF) which results
in incorrect offsets.
Are you going to file a bug for GCC?
BTW: Nice testcase
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-09-14 7:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <88072818E0A3D742B2B1AF16BBEC65A7263D8247@IRSMSX107.ger.corp.intel.com>
[not found] ` <20160707095439.GA6792@host1.jankratochvil.net>
[not found] ` <88072818E0A3D742B2B1AF16BBEC65A7263D990E@IRSMSX107.ger.corp.intel.com>
[not found] ` <20160714182743.GA10672@host1.jankratochvil.net>
[not found] ` <88072818E0A3D742B2B1AF16BBEC65A7263E6F2E@IRSMSX107.ger.corp.intel.com>
[not found] ` <20160715091352.GA8059@host1.jankratochvil.net>
[not found] ` <88072818E0A3D742B2B1AF16BBEC65A7263E8FD9@IRSMSX107.ger.corp.intel.com>
[not found] ` <20160716151310.GA14331@host1.jankratochvil.net>
[not found] ` <20160716151837.GA797@host1.jankratochvil.net>
[not found] ` <88072818E0A3D742B2B1AF16BBEC65A7263F0988@IRSMSX107.ger.corp.intel.com>
2016-08-16 13:59 ` Jan Kratochvil
2016-08-19 9:58 ` Bernhard Heckel
2016-08-21 17:04 ` Jan Kratochvil
2016-08-23 13:34 ` Bernhard Heckel
2016-08-25 17:06 ` Jan Kratochvil
2016-08-25 17:22 ` Jan Kratochvil
2016-08-26 7:17 ` Jan Kratochvil
2016-09-01 10:11 ` Bernhard Heckel
2016-09-02 13:44 ` Bernhard Heckel
2016-09-04 17:15 ` Jan Kratochvil
2016-09-07 10:29 ` Bernhard Heckel
2016-09-07 20:05 ` Jan Kratochvil
2016-09-12 21:05 ` Jan Kratochvil
2016-09-14 7:24 ` Bernhard Heckel [this message]
2016-09-14 12:53 ` Jan Kratochvil
2016-09-07 20:24 ` Jan Kratochvil
2016-09-01 9:48 ` Jan Kratochvil
2015-01-14 13:49 Keven Boell
2015-05-28 20:36 ` Jan Kratochvil
2015-05-28 20:52 ` Joel Brobecker
2015-06-14 8:15 ` Jan Kratochvil
2015-06-17 11:42 ` Boell, Keven
2015-07-01 12:43 ` Keven Boell
2016-07-07 8:30 ` Jan Kratochvil
2016-07-07 9:16 ` Bernhard Heckel
2016-07-07 9:23 ` 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=57D8FB1F.1040000@intel.com \
--to=bernhard.heckel@intel.com \
--cc=christoph.t.weinmann@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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