From: Jim Blandy <jimb@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Daniel Jacobowitz <drow@false.org>,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com, Keith Seitz <keiths@redhat.com>,
Andrew Cagney <cagney@gnu.org>
Subject: Re: RFA: patch to fix gdb/1680
Date: Sat, 19 Jun 2004 06:15:00 -0000 [thread overview]
Message-ID: <vt2ekocrs4h.fsf@zenia.home> (raw)
In-Reply-To: <jeekocfpke.fsf@sykes.suse.de>
Andreas Schwab <schwab@suse.de> writes:
> Jim Blandy <jimb@redhat.com> writes:
>
> > Ahh. Here is a revision of my patch. It is tested under the same
> > configuration as the original patch.
> >
> > 2004-06-17 Jim Blandy <jimb@redhat.com>
> >
> > Fix PR testsuite/1680.
> > * gdb.arch/i386-sse.exp: Don't use curly braces in regular
> > expressions.
>
> How about "Quote curly braces in regular expressions"?
But that would describe my patch correctly. Whose side are you on,
anyway?
(Thanks for noticing this; corrected as suggested. And thanks to
Michael, too.)
2004-06-17 Jim Blandy <jimb@redhat.com>
Fix PR testsuite/1680.
* gdb.arch/i386-sse.exp: Properly quote 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 18 Jun 2004 22:15:52 -0000
*************** gdb_continue_to_breakpoint "continue to
*** 71,77 ****
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"
}
--- 71,77 ----
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"
}
*************** gdb_continue_to_breakpoint "continue to
*** 86,91 ****
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\]"
}
--- 86,91 ----
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\]"
}
next prev parent reply other threads:[~2004-06-19 6:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 2:44 Michael Elizabeth Chastain
[not found] <1087626323.4926.ezmlm@sources.redhat.com>
2004-06-20 22:37 ` Jim Ingham
2004-06-19 6:31 Michael Elizabeth Chastain
2004-06-21 5:00 ` Jim Blandy
2004-06-19 2:44 Michael Elizabeth Chastain
2004-06-19 6:25 ` Joel Brobecker
2004-06-18 23:38 Michael Elizabeth Chastain
2004-06-18 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz
2004-06-18 19:43 Michael Elizabeth Chastain
2004-06-18 18:25 Michael Elizabeth Chastain
2004-06-18 18:10 Jim Blandy
2004-06-18 18:42 ` Daniel Jacobowitz
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=vt2ekocrs4h.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=schwab@suse.de \
/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