This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFA] testsuite tweak for Arm big-endian


Somebody tell me if this looks right.
It fixes a failure in long_long.exp for big-endian arm.
2002-11-06  Michael Snyder  <msnyder@redhat.com>

	* gdb.base/long_long.exp: In special case code for arm, 
	differentiate between big-endian and little-endian floats.

Index: long_long.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/long_long.exp,v
retrieving revision 1.12
diff -p -r1.12 long_long.exp
*** long_long.exp	6 Jun 2002 19:08:18 -0000	1.12
--- long_long.exp	7 Nov 2002 00:08:48 -0000
*************** if { $sizeof_double == 8 || $sizeof_long
*** 159,167 ****
      # but a hybrid.  They are in little endian format with the two words
      # swapped in big endian format.
  
!     if { [istarget "arm*-*-*"] || \
  	    [istarget "xscale*-*-*"] || \
! 	    [istarget "strongarm*-*-*"] } then {
  	# assume the long long represents a floating point double in ARM format
  	gdb_test "p/f oct" ".*2.1386676354387559e\\+265.*"
      } else {
--- 159,168 ----
      # but a hybrid.  They are in little endian format with the two words
      # swapped in big endian format.
  
!     if { ([istarget "arm*-*-*"] || \
  	    [istarget "xscale*-*-*"] || \
! 	    [istarget "strongarm*-*-*"]) && \
! 	$target_bigendian_p == 0 } then {
  	# assume the long long represents a floating point double in ARM format
  	gdb_test "p/f oct" ".*2.1386676354387559e\\+265.*"
      } else {

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]