From: Luis Machado <lgustavo@codesourcery.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, testsuite] Don't run SREC, IHEX and TEKHEX tests for MIPS N64.
Date: Tue, 02 Jul 2013 14:45:00 -0000 [thread overview]
Message-ID: <51D2E779.4040209@codesourcery.com> (raw)
In-Reply-To: <51D2E59E.7080300@codesourcery.com>
On 07/02/2013 11:37 AM, Yao Qi wrote:
> On 07/02/2013 12:24 AM, Luis Machado wrote:
>> +# Since SREC, IHEX and TEKHEX cannot handle 64-bit addresses for
>> +# MIPS64, stop testing if we have a 64-bit MIPS program.
>> +if {[istarget "mips*-*-*"]} then {
>> + send_gdb "show mips abi\n"
>> + gdb_expect {
>> + -re ".*n64.*$gdb_prompt $" {
>> + set is64bitonly "yes"
>> + }
>> + }
>> +}
>> +
>
> Luis,
> this patch looks reasonable to me. Probably, we should move the code to
> the place close to the existing code setting "is64bitonly" too.
>
For MIPS we need to load the binary first to be able to tell if we
really have a N64 ABI or not. That is why this check is a bit later in
the code compared to the other checks.
Does that make sense?
Luis
next prev parent reply other threads:[~2013-07-02 14:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:24 Luis Machado
2013-07-02 14:37 ` Yao Qi
2013-07-02 14:45 ` Luis Machado [this message]
2013-07-03 0:03 ` Yao Qi
2013-07-02 16:47 ` Tom Tromey
2013-07-02 16:51 ` Luis Machado
2013-07-02 17:19 ` Stan Shebs
2013-07-02 18:10 ` Tom Tromey
2013-07-02 18:50 ` Luis Machado
2013-07-02 20:55 ` Tom Tromey
2013-07-03 15:05 ` Pedro Alves
2013-07-03 19:23 ` Luis Machado
2013-07-03 19:26 ` Pedro Alves
2013-07-03 20:19 ` Luis Machado
2013-07-04 8:11 ` Pedro Alves
2013-07-06 2:41 ` Luis Machado
2013-07-03 20:35 ` Maciej W. Rozycki
2013-07-03 20:54 ` Luis Machado
2013-07-03 21:08 ` Maciej W. Rozycki
2013-07-04 11:48 ` Luis Machado
2013-07-04 12:13 ` Maciej W. Rozycki
2013-07-04 12:21 ` Luis Machado
2013-07-04 13:22 ` Ulrich Weigand
2013-07-04 13:24 ` Luis Machado
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=51D2E779.4040209@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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