From: Joel Brobecker <brobecker@adacore.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V2 1/2] testsuite: Fix timeout issues during print of vla-arrays.
Date: Fri, 26 Feb 2016 16:44:00 -0000 [thread overview]
Message-ID: <20160226164445.GD5599@adacore.com> (raw)
In-Reply-To: <1456405685-4237-1-git-send-email-bernhard.heckel@intel.com>
> 2016-02-12 Bernhard Heckel <bernhard.heckel@intel.com>
>
> gdb/Changelog:
>
> * vla-history.exp: Lookup array elements and printing exceeds timeout.
This is OK.
> Conflicts:
>
> gdb/testsuite/gdb.fortran/vla-history.exp
> gdb/testsuite/gdb.fortran/vla-value.exp
Please remove these from the commit log! ;-)
--
Joel
next prev parent reply other threads:[~2016-02-26 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 13:08 Bernhard Heckel
2016-02-25 13:08 ` [PATCH V2 2/2] testsuite: Remove unnecessarry code in fortran vla-history test Bernhard Heckel
2016-02-26 14:50 ` Luis Machado
2016-02-26 16:45 ` Joel Brobecker
2016-03-02 15:46 ` Heckel, Bernhard
2016-02-26 14:46 ` [PATCH V2 1/2] testsuite: Fix timeout issues during print of vla-arrays Luis Machado
2016-02-26 16:44 ` Joel Brobecker [this message]
2016-03-02 15:47 ` Heckel, Bernhard
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=20160226164445.GD5599@adacore.com \
--to=brobecker@adacore.com \
--cc=bernhard.heckel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).