From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, GDB] Expect prompt after no FPU warning
Date: Thu, 18 May 2017 15:46:00 -0000 [thread overview]
Message-ID: <d54d9f5a-ca86-a81b-8ae4-f059527b6670@foss.arm.com> (raw)
In-Reply-To: <86wp9f8v4g.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
FYI
On 17/05/17 14:34, Yao Qi wrote:
> Thomas Preudhomme <thomas.preudhomme@foss.arm.com> writes:
>
>> Is this ok for master branch and GDB 8 (after a 1 week period)?
>>
>
> Patch is good to me, one comment below.
>
> GDB 8 will be released soon, so it is good to have this patch in 8.0.
> This patch is about test case, so it should be safe to merge it to 8.0
> branch now.
>
>> - gdb_test "info float" "No floating.point info available for this processor." "info float (unknown target)"
>> + gdb_test "info float" "No floating.point info available for this processor.*$gdb_prompt $" "info float (unknown target)"
>> }
>
> This change is not needed, because $gdb_prompt is appended in the
> pattern inside of gdb_test.
>
Alright, pushed the attached patch which also fix a spurious codestyle change
(tab - space) to master and GDB 8.
Best regards,
Thomas
[-- Attachment #2: nofloat_gdb_tests_expect_prompt.patch --]
[-- Type: text/x-patch, Size: 1977 bytes --]
diff --git a/gdb/testsuite/gdb.base/float.exp b/gdb/testsuite/gdb.base/float.exp
index a4762c9742682391074f0707e56a6eae4cd70c6e..e09c124b8825d687cd0bac9f363b0b61b0ed9230 100644
--- a/gdb/testsuite/gdb.base/float.exp
+++ b/gdb/testsuite/gdb.base/float.exp
@@ -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 $" {
pass "info float (without FPU)"
}
}
@@ -63,7 +63,7 @@ if { [is_aarch64_target] } then {
-re "fp0.*fp1.*fp7.*$gdb_prompt $" {
pass "info float (with FPU)"
}
- -re "No floating.point info available for this processor.*" {
+ -re "No floating.point info available for this processor.*$gdb_prompt $" {
pass "info float (without FPU)"
}
}
@@ -81,7 +81,7 @@ if { [is_aarch64_target] } then {
-re "fd0.*fd3.*$gdb_prompt $" {
pass "info float (with FPU)"
}
- -re "No floating.point info available for this processor.*" {
+ -re "No floating.point info available for this processor.*$gdb_prompt $" {
pass "info float (without FPU)"
}
}
@@ -90,7 +90,7 @@ if { [is_aarch64_target] } then {
-re "f0.*f1.*f31.*fpscr.*$gdb_prompt $" {
pass "info float (with FPU)"
}
- -re "No floating.point info available for this processor.*" {
+ -re "No floating.point info available for this processor.*$gdb_prompt $" {
pass "info float (without FPU)"
}
}
@@ -102,7 +102,7 @@ if { [is_aarch64_target] } then {
-re "fpul.*fr0.*fr1.*fr15.*$gdb_prompt $" {
pass "info float (with FPU)"
}
- -re "No floating.point info available for this processor.*" {
+ -re "No floating.point info available for this processor.*$gdb_prompt $" {
pass "info float (without FPU)"
}
}
prev parent reply other threads:[~2017-05-18 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 9:13 [PATCH, GDB/ARM] " Thomas Preudhomme
2017-05-17 12:10 ` Yao Qi
2017-05-17 12:20 ` Thomas Preudhomme
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 [this message]
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=d54d9f5a-ca86-a81b-8ae4-f059527b6670@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).