From: Andreas Schwab <schwab@suse.de>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] changed output in altivec-regs.exp
Date: Mon, 05 Mar 2007 22:05:00 -0000 [thread overview]
Message-ID: <jetzwz8hyw.fsf@sykes.suse.de> (raw)
In-Reply-To: <1173125923.21352.34.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Mon, 05 Mar 2007 17:18:43 -0300")
Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> Hi,
>
> This makes the test script expect the new output of the "show endian"
> command, which for PPC architecture changed sometime between GDB 6.5 and
> GDB 6.6.
>
> 2007-03-05 Thiago Jung Bauermann <bauerman@br.ibm.com>
>
> * gdb.arch/altivec-regs.exp: Match new "show endian" output.
This has already been fixed properly a few weeks ago.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2007-03-05 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:18 Thiago Jung Bauermann
2007-03-05 20:30 ` Daniel Jacobowitz
2007-03-06 18:47 ` Thiago Jung Bauermann
2007-03-05 22:05 ` Andreas Schwab [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=jetzwz8hyw.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bauerman@br.ibm.com \
--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