Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: [PATCH] Testing tweaks for xscale
Date: Wed, 08 May 2002 08:29:00 -0000	[thread overview]
Message-ID: <200205081528.QAA18424@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 03 May 2002 14:11:31 PDT." <200205032111.g43LBVJ27680@reddwarf.sfbay.redhat.com>

> 2002-05-02  Michael Snyder  <msnyder@redhat.com>
> 
> 	* gdb.base/long_long.exp: Add xscale target.
> 	* gdb.base/default.exp: Add xscale target.
> 
> Index: gdb.base/default.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/default.exp,v
> retrieving revision 1.9
> diff -p -r1.9 default.exp
> *** gdb.base/default.exp	29 Mar 2002 01:19:11 -0000	1.9
> --- gdb.base/default.exp	3 May 2002 21:23:13 -0000
> *************** gdb_test "info files" "" "info files"
> *** 348,353 ****
> --- 348,355 ----
>   #test info float
>   if [istarget "arm*-*-*"] then {
>       gdb_test "info float" "Software FPU type.*mask:.*flags:.*" "info float"
> + } elseif [istarget "xscale*-*-*"] then {
> +     gdb_test "info float" "Software FPU type.*mask:.*flags:.*" "info float"
>   } elseif [istarget "thumb*-*-*"] then {
>       gdb_test "info float" "Software FPU type.*mask:.*flags:.*" "info float"
>   } elseif [istarget "strongarm*-*-*"] then {
> Index: gdb.base/long_long.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/long_long.exp,v
> retrieving revision 1.7
> diff -p -r1.7 long_long.exp
> *** gdb.base/long_long.exp	17 Jul 2001 22:19:49 -0000	1.7
> --- gdb.base/long_long.exp	3 May 2002 21:23:13 -0000
> *************** if { $sizeof_double == 8 } {
> *** 157,162 ****
> --- 157,167 ----
>   #   assume the long long represents a floating point double in ARM format
>        gdb_test "p/f oct" ".*2.1386676354387559e\\+265.*"
>   
> +   } elseif [ istarget "xscale*-*-*" ] then {
> + 
> + #   assume the long long represents a floating point double in ARM format
> +      gdb_test "p/f oct" ".*2.1386676354387559e\\+265.*"
> + 
>     } else {
>   
>   #   assume the long long represents a floating point double in little

I'm assuming here that maintainership of the ARM parts includes changes 
like this to the testsuite...

Two points.

1) Since xscale is an ARM processor variant, I think these should be kept 
as a single "if" clause -- clearly we intend to do the same thing for both.

2) The following thumb clause is, I think, now dead -- thumb support has 
been rolled into the ARM configuration.

So I think the first change should be something like

   if {[istarget "arm*-*-*"] || [istarget "xscale*-*-*"] 
       || [istarget "strongarm*-*-*"]} then {
       gdb_test "info float" "Software FPU type.*mask:.*flags:.*" "info 
float"
   } else {.... non-arm things...

R.



  reply	other threads:[~2002-05-08 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 14:24 Michael Snyder
2002-05-08  8:29 ` Richard Earnshaw [this message]
2002-05-08 14:03   ` Michael Snyder
2002-05-09  2:14     ` Richard Earnshaw

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=200205081528.QAA18424@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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