Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: patch to fix gdb/1680
Date: Fri, 18 Jun 2004 18:10:00 -0000	[thread overview]
Message-ID: <vt2vfhou48t.fsf@zenia.home> (raw)


I tested it on my machine.  i686-pc-linux-gnu, gcc 3.3, dwarf-2 and
stabs+.

Expect version is       5.26
Tcl version is          8.4
Framework version is    1.4.2.x

2004-06-17  Jim Blandy  <jimb@redhat.com>

	* gdb.arch/i386-sse.exp: Don't use curly braces in regular
	expressions.

Index: gdb/testsuite/gdb.arch/i386-sse.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/i386-sse.exp,v
retrieving revision 1.1
diff -c -p -r1.1 i386-sse.exp
*** gdb/testsuite/gdb.arch/i386-sse.exp	7 Jun 2004 15:38:52 -0000	1.1
--- gdb/testsuite/gdb.arch/i386-sse.exp	17 Jun 2004 22:55:22 -0000
*************** gdb_test "break [gdb_get_line_number "fi
*** 70,77 ****
  gdb_continue_to_breakpoint "continue to first breakpoint in main"
  
  foreach r {0 1 2 3 4 5 6 7} {
      gdb_test "print \$xmm$r.v4_float" \
!         ".. = {$r, $r.25, $r.5, $r.75}.*" \
          "check contents of %xmm$r"
  }
  
--- 70,79 ----
  gdb_continue_to_breakpoint "continue to first breakpoint in main"
  
  foreach r {0 1 2 3 4 5 6 7} {
+     # Avoid using curly braces in regular expressions; different
+     # versions of Tcl treat them differently.
      gdb_test "print \$xmm$r.v4_float" \
!         ".. = .$r, $r.25, $r.5, $r.75..*" \
          "check contents of %xmm$r"
  }
  
*************** gdb_test "break [gdb_get_line_number "se
*** 85,91 ****
  gdb_continue_to_breakpoint "continue to second breakpoint in main"
  
  foreach r {0 1 2 3 4 5 6 7} {
      gdb_test "print data\[$r\]" \
!         ".. = {f = {[expr $r + 10], $r.25, $r.5, $r.75}}.*" \
          "check contents of data\[$r\]"
  }
--- 87,95 ----
  gdb_continue_to_breakpoint "continue to second breakpoint in main"
  
  foreach r {0 1 2 3 4 5 6 7} {
+     # Avoid using curly braces in regular expressions; different
+     # versions of Tcl treat them differently.
      gdb_test "print data\[$r\]" \
!         ".. = .f = .[expr $r + 10], $r.25, $r.5, $r.75...*" \
          "check contents of data\[$r\]"
  }


             reply	other threads:[~2004-06-18 18:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 18:10 Jim Blandy [this message]
2004-06-18 18:42 ` Daniel Jacobowitz
2004-06-18 18:25 Michael Elizabeth Chastain
2004-06-18 19:18 Michael Elizabeth Chastain
2004-06-18 19:35 ` Andrew Cagney
2004-06-18 19:42 ` Daniel Jacobowitz
2004-06-18 19:56   ` Andrew Cagney
2004-06-18 20:00     ` Daniel Jacobowitz
2004-06-18 22:20   ` Jim Blandy
2004-06-18 22:51     ` Andreas Schwab
2004-06-19  6:15       ` Jim Blandy
2004-06-18 19:43 Michael Elizabeth Chastain
2004-06-18 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz
2004-06-18 23:38 Michael Elizabeth Chastain
2004-06-19  2:44 Michael Elizabeth Chastain
2004-06-19  6:25 ` Joel Brobecker
2004-06-19  6:31 Michael Elizabeth Chastain
2004-06-21  5:00 ` Jim Blandy
     [not found] <1087626323.4926.ezmlm@sources.redhat.com>
2004-06-20 22:37 ` Jim Ingham
2004-06-21  2:44 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=vt2vfhou48t.fsf@zenia.home \
    --to=jimb@redhat.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