Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Fix selftest.exp
Date: Sun, 20 Jul 2003 15:52:00 -0000	[thread overview]
Message-ID: <20030720155257.GA8102@nevyn.them.org> (raw)
In-Reply-To: <m38yqty5g0.fsf@whitebox.as.local>

On Sun, Jul 20, 2003 at 10:21:03AM +0200, Andreas Schwab wrote:
> GCC 3.4 can reorder insns quite heavily.  On PPC the selftest fails
> because (parts of) later statements are executed much earlier in the
> function.
> 
> Andreas.

This is OK.  I hate this test...

> 2003-07-20  Andreas Schwab  <schwab@suse.de>
> 
> 	* gdb.base/selftest.exp (do_steps_and_nexts): Add more patterns
> 	due to insn reordering.
> 
> --- gdb/testsuite/gdb.base/selftest.exp.~1.8.6.1.~	2003-06-30 23:06:56.000000000 +0200
> +++ gdb/testsuite/gdb.base/selftest.exp	2003-07-20 10:11:30.000000000 +0200
> @@ -180,6 +180,18 @@ proc do_steps_and_nexts {} {
>  		set description "step over gdb_sysroot initialization"
>  		set command "step"
>  	    }
> +	    -re ".*ndir = 0.*$gdb_prompt $" {
> +		set description "step over ndir initialization"
> +		set command "step"
> +	    }
> +	    -re ".*instream = stdin.*$gdb_prompt $" {
> +		set description "step over instream initialization"
> +		set command "step"
> +	    }
> +	    -re ".*getcwd .gdb_dirbuf, sizeof .gdb_dirbuf..;.*$gdb_prompt $" {
> +		set description "next over getcwd"
> +		set command "next"
> +	    }
>  	    -re "\[ \t\]+\{\r\n$gdb_prompt $" {
>  		setup_xfail "mips-*-irix5*"
>  		fail "$description ended up at odd location"
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-07-20 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20  8:21 Andreas Schwab
2003-07-20 15:52 ` Daniel Jacobowitz [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=20030720155257.GA8102@nevyn.them.org \
    --to=drow@mvista.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