Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [PATCH, M68K] Support xml testsuite
Date: Tue, 17 Nov 2009 12:36:00 -0000	[thread overview]
Message-ID: <4B02989B.3070000@codesourcery.com> (raw)
In-Reply-To: <4B029388.5070001@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 194 bytes --]

Hi,

This simple patch adds support for the gdb.xml testsuite for M68K and 
ColdFire targets.

OK to apply?

Regards,

-- 
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724

[-- Attachment #2: fsf-gdb-m68k-testsuite.ChangeLog --]
[-- Type: text/plain, Size: 189 bytes --]

2009-11-17  Nathan Sidwell  <nathan@codesourcery.com>

	* features/m68k-core.xml: New file.

2009-11-17  Nathan Sidwell  <nathan@codesourcery.com>

	* gdb.xml/tdesc-regs.exp: Use for m68k.

[-- Attachment #3: fsf-gdb-m68k-testsuite.patch --]
[-- Type: text/plain, Size: 1730 bytes --]

 ChangeLog.testsuite                  |    6 ++++++
 gdb/features/m68k-core.xml           |   24 ++++++++++++++++++++++++
 gdb/testsuite/gdb.xml/tdesc-regs.exp |    3 +++
 3 files changed, 33 insertions(+), 0 deletions(-)

diff --git a/gdb/features/m68k-core.xml b/gdb/features/m68k-core.xml
new file mode 100644
index 0000000..f0b3d30
--- /dev/null
+++ b/gdb/features/m68k-core.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0"?>
+<!DOCTYPE feature SYSTEM "gdb-target.dtd">
+<feature name="org.gnu.gdb.coldfire.core">
+  <reg name="d0" bitsize="32"/>
+  <reg name="d1" bitsize="32"/>
+  <reg name="d2" bitsize="32"/>
+  <reg name="d3" bitsize="32"/>
+  <reg name="d4" bitsize="32"/>
+  <reg name="d5" bitsize="32"/>
+  <reg name="d6" bitsize="32"/>
+  <reg name="d7" bitsize="32"/>
+  <reg name="a0" bitsize="32" type="data_ptr"/>
+  <reg name="a1" bitsize="32" type="data_ptr"/>
+  <reg name="a2" bitsize="32" type="data_ptr"/>
+  <reg name="a3" bitsize="32" type="data_ptr"/>
+  <reg name="a4" bitsize="32" type="data_ptr"/>
+  <reg name="a5" bitsize="32" type="data_ptr"/>
+  <reg name="fp" bitsize="32" type="data_ptr"/>
+  <reg name="sp" bitsize="32" type="data_ptr"/>
+
+  <reg name="ps" bitsize="32"/>
+  <reg name="pc" bitsize="32" type="code_ptr"/>
+
+</feature>
diff --git a/gdb/testsuite/gdb.xml/tdesc-regs.exp b/gdb/testsuite/gdb.xml/tdesc-regs.exp
index cc61cd0..958b18f 100644
--- a/gdb/testsuite/gdb.xml/tdesc-regs.exp
+++ b/gdb/testsuite/gdb.xml/tdesc-regs.exp
@@ -32,6 +32,9 @@ switch -glob -- [istarget] {
     "xscale-*-*" {
         set core-regs {arm-core.xml}
     }
+    "*m68k-*-*" {
+        set core-regs {m68k-core.xml}
+    }
     "mips*-*-*" {
 	set core-regs {mips-cpu.xml mips-cp0.xml mips-fpu.xml}
     }

  parent reply	other threads:[~2009-11-17 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 12:15 [PATCHES, M68K] Various fixes and improvements for M68K and ColdFire Maxim Kuvyrkov
2009-11-17 12:22 ` [PATCH, M68K] Handle lack of FPU registers Maxim Kuvyrkov
2009-11-17 12:28 ` [PATCH, M68K] Add regformat file for ColdFire registers Maxim Kuvyrkov
2009-11-17 12:34 ` [PATCH, M68K] Fix initialization Maxim Kuvyrkov
2009-11-17 12:36 ` Maxim Kuvyrkov [this message]
2009-11-17 15:40 ` [PATCHES, M68K] Various fixes and improvements for M68K and ColdFire Daniel Jacobowitz

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=4B02989B.3070000@codesourcery.com \
    --to=maxim@codesourcery.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