From: Richard Bunt <Richard.Bunt@arm.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: New FAILs on gdb.fortran/short-circuit-argument-list.exp when testing on native{,-extended}-gdbserver
Date: Mon, 03 Dec 2018 13:22:00 -0000 [thread overview]
Message-ID: <965a7051-54ec-3f4b-7a6d-3bc057a2dcc0@arm.com> (raw)
In-Reply-To: <87h8hypcd1.fsf_-_@redhat.com>
Hi Sergio,
My apologies, I completely missed this reply. I'll investigate these failures.
Rich.
On 10/7/18 6:14 AM, Sergio Durigan Junior wrote:
> On Tuesday, September 18 2018, Richard Bunt wrote:
>
>> On 09/14/2018 10:00 PM, Tom Tromey wrote:
>>>>>>>> "Richard" == Richard Bunt <richard.bunt@arm.com> writes:
>>>
>>> Richard> Version 3 addresses review comments:
>>>
>>> Richard> * Removed forward declaration of skip_undetermined_arglist.
>>> Richard> * Made definition of skip_undetermined_arglist static.
>>> Richard> * Added introductory comment to skip_undetermined_arglist.
>>> Richard> * Dropped (*pos)+=3 into the block.
>>> Richard> * Adjusted Tcl bracing.
>>> Richard> * Removed string splitting in the test case.
>>>
>>> Thanks again for the patch.
>>>
>>> Richard> + if (noside != EVAL_SKIP)
>>> Richard> + {
>>> Richard> + return evaluate_var_value (noside, exp->elts[pc + 1].block, var);
>>> Richard> + }
>>>
>>> The gdb style is no braces if there's just a single line.
>>>
>>> Richard> + else
>>> Richard> + {
>>> Richard> + /* Return a dummy value of the correct type when skipping, so
>>> Richard> + that parent functions know what is to be skipped. */
>>> Richard> + return allocate_value (SYMBOL_TYPE (var));
>>>
>>> ... compared to here, where braces are mandatory.
>>>
>>> This patch is ok with that first set of braces removed.
>>> (You don't have to re-send it.)
>>>
>>> thanks,
>>> Tom
>>>
>>
>> Many thanks for reviewing this change. I will fix up the braces and push.
>
> Hi Richard,
>
> Just a heads up, I've noticed a few failures when running
> gdb.fortran/short-circuit-argument-list.exp on a
> native{,-extended}-gdbserver board:
>
> FAIL: gdb.fortran/short-circuit-argument-list.exp: arg=No: p function_no_arg_false() .OR. function_no_arg()
> FAIL: gdb.fortran/short-circuit-argument-list.exp: arg=One: p function_no_arg_false() .OR. function_one_arg( .TRUE.)
> FAIL: gdb.fortran/short-circuit-argument-list.exp: arg=Two: p function_no_arg_false() .OR. function_two_arg( .TRUE., .TRUE.)
> FAIL: gdb.fortran/short-circuit-argument-list.exp: p function_one_arg(.FALSE. .OR. function_no_arg())
> FAIL: gdb.fortran/short-circuit-argument-list.exp: p function_one_arg(.TRUE. .OR. function_no_arg())
>
> The failures are easily reproducible, but let me know if you need a
> gdb.log excerpt. I haven't had the time to investigate them further.
>
> Thanks,
>
next prev parent reply other threads:[~2018-12-03 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:10 [PATCH v3] Logical short circuiting with argument lists Richard Bunt
2018-09-14 21:00 ` Tom Tromey
2018-09-18 18:39 ` Richard Bunt
2018-10-07 5:14 ` New FAILs on gdb.fortran/short-circuit-argument-list.exp when testing on native{,-extended}-gdbserver (was: Re: [PATCH v3] Logical short circuiting with argument lists) Sergio Durigan Junior
2018-12-03 13:22 ` Richard Bunt [this message]
2018-12-03 14:58 ` New FAILs on gdb.fortran/short-circuit-argument-list.exp when testing on native{,-extended}-gdbserver Richard Bunt
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=965a7051-54ec-3f4b-7a6d-3bc057a2dcc0@arm.com \
--to=richard.bunt@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).