Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
	Stan Shebs <stanshebs@earthlink.net>,
	 GDB Patches <gdb-patches@sourceware.org>,
	Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [PATCH, testsuite] Don't run SREC, IHEX and TEKHEX tests for MIPS N64.
Date: Sat, 06 Jul 2013 02:41:00 -0000	[thread overview]
Message-ID: <51D783AE.50906@codesourcery.com> (raw)
In-Reply-To: <51D52E02.4020607@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

On 07/04/2013 05:10 AM, Pedro Alves wrote:
> On 07/03/2013 09:19 PM, Luis Machado wrote:
>> On 07/03/2013 04:25 PM, Pedro Alves wrote:
>
>>> But do you see a problem with checking whether "&intarray is < 32-bit" instead?
>>>
>>
>> Not really. Like so?
>
> Yep, exactly like that.
>
> Thanks,
>

Thanks. Here is what i checked in. I restored the SPU exception.

Luis

[-- Attachment #2: dump_exp.diff --]
[-- Type: text/x-patch, Size: 1560 bytes --]

2013-07-05  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/dump.exp: Remove arch-specific tests and do a
	generic data address check to set is64bitonly correctly.

diff --git a/gdb/testsuite/gdb.base/dump.exp b/gdb/testsuite/gdb.base/dump.exp
index ea93b89..eb9be90 100644
--- a/gdb/testsuite/gdb.base/dump.exp
+++ b/gdb/testsuite/gdb.base/dump.exp
@@ -30,10 +30,6 @@ if [istarget "alpha*-*-*"] then {
     lappend options "additional_flags=-Wl,-taso"
 }
 
-if {[istarget "ia64*-*-*"] || [istarget "hppa64-*-*"]} then {
-    set is64bitonly "yes"
-}
-
 if {[istarget "spu*-*-*"]} then {
     # The internal address format used for the combined Cell/B.E.
     # debugger requires 64-bit.
@@ -56,6 +52,15 @@ gdb_test "dump mem /dev/null 0x10 0x20" "Cannot access memory at address 0x10" \
 
 gdb_load ${binfile}
 
+# Check the address of a variable.  If it is bigger than 32-bit,
+# assume our target has 64-bit addresses that are not supported by SREC,
+# IHEX and TEKHEX.  We skip those tests then.
+set max_32bit_address "0xffffffff"
+set data_address [get_hexadecimal_valueof "&intarray" 0x100000000]
+if {${data_address} > ${max_32bit_address}} then {
+    set is64bitonly "yes"
+}
+
 # Clean up any stale output files from previous test runs
 
 remote_exec build "rm -f intarr1.bin intarr1b.bin intarr1.ihex intarr1.srec intarr1.tekhex intarr2.bin intarr2b.bin intarr2.ihex intarr2.srec intarr2.tekhex intstr1.bin intstr1b.bin intstr1.ihex intstr1.srec intstr1.tekhex intstr2.bin intstr2b.bin intstr2.ihex intstr2.srec intstr2.tekhex intarr3.srec"

  reply	other threads:[~2013-07-06  2:41 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
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 [this message]
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=51D783AE.50906@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@redhat.com \
    --cc=uweigand@de.ibm.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