public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, GDB/ARM] Expect prompt after no FPU warning
Date: Wed, 17 May 2017 12:20:00 -0000	[thread overview]
Message-ID: <e32303d9-cdc3-ab93-a4d1-d9d5877abef8@foss.arm.com> (raw)
In-Reply-To: <861srnadl8.fsf@gmail.com>



On 17/05/17 13:10, Yao Qi wrote:
> Thomas Preudhomme <thomas.preudhomme@foss.arm.com> writes:
>
>> 2017-04-27  Thomas Preud'homme  <thomas.preudhomme@arm.com>
>>
>> 	* gdb.base/float.exp (info float): Expect GDB prompt for ARM
>
> Remove " (info float)".
>
>> 	targets without FPU.
>>
>
>
>> @@ -50,7 +50,7 @@ if { [is_aarch64_target] } then {
>>  	    # if we have NEON.
>>  	    pass "info float (VFP)"
>>  	}
>> -        -re "No floating.point info available for this processor.*" {
>> +        -re "No floating.point info available for this processor.*$gdb_prompt $" {
>
> The fix is right but it can be applied to all archs which may not have
> FPU.  If you search "N floating.point info", you can find multiple hits.
> $gdb_prompt is needed for all of them.

Err yes sorry, I didn't add it because I only tested on ARM. I'll update the 
patch. Thanks!

Best regards,

Thomas

  reply	other threads:[~2017-05-17 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  9:13 Thomas Preudhomme
2017-05-17 12:10 ` Yao Qi
2017-05-17 12:20   ` Thomas Preudhomme [this message]
2017-05-17 12:53     ` [PATCH, GDB] " Thomas Preudhomme
2017-05-17 13:34       ` Yao Qi
2017-05-17 14:49         ` Thomas Preudhomme
2017-05-18 15:46         ` Thomas Preudhomme

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=e32303d9-cdc3-ab93-a4d1-d9d5877abef8@foss.arm.com \
    --to=thomas.preudhomme@foss.arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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).