From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: "Weinmann, Christoph T" <christoph.t.weinmann@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [V4 00/21] Fortran dynamic array support
Date: Sun, 21 Aug 2016 17:04:00 -0000 [thread overview]
Message-ID: <20160821170346.GA21909@host1.jankratochvil.net> (raw)
In-Reply-To: <57B6D831.4080605@intel.com>
On Fri, 19 Aug 2016 11:58:09 +0200, Bernhard Heckel wrote:
> here is the missing patch in your environment.
> https://sourceware.org/ml/gdb-patches/2015-01/msg00385.html
> This patch handles strides in DWARF and your fortran program.
OK, thanks, it does fix:
-FAIL: gdb.fortran/dynamic.exp: p varw filled
+PASS: gdb.fortran/dynamic.exp: p varw filled
-FAIL: gdb.fortran/vla-stride.exp: print odd-elements
+PASS: gdb.fortran/vla-stride.exp: print odd-elements
-FAIL: gdb.fortran/vla-stride.exp: print last odd-element
+PASS: gdb.fortran/vla-stride.exp: print last odd-element
Although it regresses:
print pvla^M
-$7 = (5)^M
-(gdb) PASS: gdb.fortran/vla-stride.exp: print single-element
+value requires 4294967288 bytes, which is more than max-value-size^M
+(gdb) FAIL: gdb.fortran/vla-stride.exp: print single-element
-$8 = 5^M
-(gdb) PASS: gdb.fortran/vla-stride.exp: print one single-element
+Insufficient memory in host GDB for object of size 4294967288 bytes, maximum allowed 536870911 bytes.^M
+(gdb) FAIL: gdb.fortran/vla-stride.exp: print one single-element
> I will create a branch about all stride patches in the next weeks.
That would be probably best, thanks.
Jan
next prev parent reply other threads:[~2016-08-21 17:04 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 [this message]
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
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=20160821170346.GA21909@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=bernhard.heckel@intel.com \
--cc=christoph.t.weinmann@intel.com \
--cc=gdb-patches@sourceware.org \
/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