Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PPC Call-clobbered registers testcase
Date: Thu, 25 Oct 2007 20:36:00 -0000	[thread overview]
Message-ID: <1193344312.4850.27.camel@localhost> (raw)
In-Reply-To: <20071025192332.GA2690@caradoc.them.org>

On Thu, 2007-10-25 at 15:23 -0400, Daniel Jacobowitz wrote:
> On Thu, Oct 25, 2007 at 04:05:27PM -0300, Luis Machado wrote:
> > Took a different path as you suggested. The synching is being done via
> > matching with the $gdb_prompt at the end of every test. This way it
> > works flawlessly on both x86 and ppc. Passes 3 tests on ppc and passes 2
> > and fails 1 on x86.
> 
> What fails on x86?  Well, I can look at it after it's in.
> 
> This is the right way to sync.
> > +    -re "\\\$$decimal = <value optimized out>\r\n$gdb_prompt" { pass "print operand1"}
> 
> "$gdb_prompt $" there please.  Ok to commit otherwise.
> 

Thanks, i've checked this in.

-- 
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com


      reply	other threads:[~2007-10-25 20:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 14:41 Luis Machado
2007-09-25 16:21 ` Luis Machado
2007-10-06 16:12   ` Daniel Jacobowitz
2007-10-08 18:55     ` Luis Machado
2007-10-08 19:06       ` Daniel Jacobowitz
2007-10-08 19:14         ` Luis Machado
2007-10-08 19:35           ` Daniel Jacobowitz
2007-10-23 22:18             ` Luis Machado
2007-10-24 21:00               ` Daniel Jacobowitz
2007-10-25 19:06                 ` Luis Machado
2007-10-25 19:30                   ` Daniel Jacobowitz
2007-10-25 20:36                     ` Luis Machado [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=1193344312.4850.27.camel@localhost \
    --to=luisgpm@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --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