From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [obvious] Indentation fixes on test sample and test file for MPX registers.
Date: Mon, 08 Jun 2015 16:06:00 -0000 [thread overview]
Message-ID: <1433779568-441-1-git-send-email-walfred.tedeschi@intel.com> (raw)
Pushing right away ok?
2015-06-08 Walfred Tedeschi <walfred.tedeschi@intel.com>
gdb/testsuite:
* gdb.arch/i386-mpx.c (have_mpx): Indentation fixed.
* gdb.arch/i386-mpx.exp: Indentation fixed.
---
gdb/testsuite/gdb.arch/i386-mpx.c | 18 +++++++++---------
gdb/testsuite/gdb.arch/i386-mpx.exp | 2 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/gdb/testsuite/gdb.arch/i386-mpx.c b/gdb/testsuite/gdb.arch/i386-mpx.c
index 87c753c..23b9650 100644
--- a/gdb/testsuite/gdb.arch/i386-mpx.c
+++ b/gdb/testsuite/gdb.arch/i386-mpx.c
@@ -35,17 +35,17 @@ have_mpx (void)
return 0;
if ((ecx & bit_OSXSAVE) == bit_OSXSAVE)
- {
- if (__get_cpuid_max (0, NULL) < 7)
- return 0;
+ {
+ if (__get_cpuid_max (0, NULL) < 7)
+ return 0;
- __cpuid_count (7, 0, eax, ebx, ecx, edx);
+ __cpuid_count (7, 0, eax, ebx, ecx, edx);
- if ((ebx & bit_MPX) == bit_MPX)
- return 1;
- else
- return 0;
- }
+ if ((ebx & bit_MPX) == bit_MPX)
+ return 1;
+ else
+ return 0;
+ }
return 0;
}
diff --git a/gdb/testsuite/gdb.arch/i386-mpx.exp b/gdb/testsuite/gdb.arch/i386-mpx.exp
index 6835b24..2db6401 100644
--- a/gdb/testsuite/gdb.arch/i386-mpx.exp
+++ b/gdb/testsuite/gdb.arch/i386-mpx.exp
@@ -30,7 +30,7 @@ if { ![istarget i?86-*-*] && ![istarget x86_64-*-* ] } {
set comp_flags "-fmpx -I${srcdir}/../nat/"
if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile} \
- [list debug nowarnings additional_flags=${comp_flags}]] } {
+ [list debug nowarnings additional_flags=${comp_flags}]] } {
return -1
}
--
2.1.4
next reply other threads:[~2015-06-08 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 16:06 Walfred Tedeschi [this message]
2015-06-09 18:24 ` Joel Brobecker
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=1433779568-441-1-git-send-email-walfred.tedeschi@intel.com \
--to=walfred.tedeschi@intel.com \
--cc=brobecker@adacore.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