Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Add sh target to float.exp
Date: Tue, 29 Jul 2003 22:30:00 -0000	[thread overview]
Message-ID: <3F26F58D.60401@redhat.com> (raw)
In-Reply-To: <yf2ispl6led.fsf@hawaii.kealia.com>

David Carlton wrote:

>On Tue, 29 Jul 2003 14:57:31 -0700, Michael Snyder <msnyder@redhat.com> said:
>  
>
>>+     send_gdb "info float\n"
>>+     gdb_expect {
>>+ 	-re ".*fpul.*fr0.*dr0.*$gdb_prompt $" {
>>+ 	    pass "info float (with FPU)"
>>+ 	}
>>+ 	-re "No floating.point info available for this processor.*$gdb_prompt $" {
>>+ 	    pass "info float (without FPU)"
>>+ 	}
>>+ 	-re ".*$gdb_prompt $" {
>>+ 	    fail "info float"
>>+ 	}
>>+ 	timeout {
>>+ 	    fail "info float (timeout)"
>>+ 	}
>>+     }
>>    
>>
>
>Does replacing the above with
>
>  gdb_test_multiple "info float" "info float" {
>  -re ".*fpul.*fr0.*dr0.*$gdb_prompt $" {
>      pass "info float (with FPU)"
>  }
>  -re "No floating.point info available for this processor.*$gdb_prompt $" {
>      pass "info float (without FPU)"
>  }
>
>work? 
>
Yep!

> Daniel's been trying to convince us to use gdb_test_multiple
>instead of gdb_expect, and it definitely saves typing once you get
>used to it.
>

I'm sold. If the patch is approved, I'll check it in in that form.




  reply	other threads:[~2003-07-29 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 21:57 Michael Snyder
2003-07-29 22:03 ` David Carlton
2003-07-29 22:30   ` Michael Snyder [this message]
2003-08-11 22:54 ` [ping] " Michael Snyder
2003-08-12  0:38   ` Elena Zannoni
2003-08-12 22:16     ` Michael Snyder
2003-08-12 22:28     ` Michael Snyder
2003-07-29 22:07 Michael Elizabeth Chastain

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=3F26F58D.60401@redhat.com \
    --to=msnyder@redhat.com \
    --cc=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.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