From: Markus Deuling <deuling@de.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA]: gdb/testsuite/gdb.arch/altivec-regs.exp Broken testcase
Date: Wed, 17 Jan 2007 04:50:00 -0000 [thread overview]
Message-ID: <45ADAAFD.20508@de.ibm.com> (raw)
In-Reply-To: <200701162128.l0GLS1U4024821@brahms.sibelius.xs4all.nl>
Hi Mark,
Mark Kettenis schrieb:
>> Date: Tue, 16 Jan 2007 07:48:18 +0100
>> From: Markus Deuling <deuling@de.ibm.com>
>>
>> Hi,
>>
>> I'm referring to http://sourceware.org/ml/gdb-patches/2007-01/msg00353.html.
>>
>> It seems that the output from "show endian" has changed since the last time someone took a
>> look into it :-) So I added a "re" to the test.
>>
>> Do we need this branch or can I delete it ?
>>>> -re "(The target endianness is set automatically .currently )(big|little)( endian.*)$gdb_prompt $" {
>>>> pass "endianness"
>>>> set endianness $expect_out(2,string)
>>>> }
>
> This worries me a bit. So in the past we were able to determine the
> endianness automagically, but now we don't? Do we understand why?
> Doesn't this mean that something is broken that worked before?
>
>
I looked into arch-utils.c. We still need that branch above. But there are also changes, so that
we need to recognize "_("The target is assumed to be big endian\n"));".
The variable "endianess" should either contain "big" or be empty in that testcase. So the way it's now with that patch should work, I think.
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next prev parent reply other threads:[~2007-01-17 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 6:48 Markus Deuling
2007-01-16 21:28 ` Mark Kettenis
2007-01-17 4:50 ` Markus Deuling [this message]
2007-01-17 5:59 ` Daniel Jacobowitz
2007-01-17 6:37 ` Markus Deuling
2007-01-17 8:31 ` Markus Deuling
2007-01-17 21:48 ` Mark Kettenis
2007-01-18 9:15 ` Markus Deuling
2007-01-20 18:32 ` 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=45ADAAFD.20508@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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