[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: binutils 2.15/ armeb-* vs. armbe-* target behavior

From: Nick Clifton
Subject: Re: binutils 2.15/ armeb-* vs. armbe-* target behavior
Date: Thu, 15 Jul 2004 17:34:00 +0100
User-agent: Mozilla Thunderbird 0.7 (X11/20040615)

Hi Lennert,

armeb-* targets generate binaries that default to big endian, but armbe-*
targets generate binaries that default to little endian (!).

If armeb-* is the preferred target format for indicating big endian mode,
perhaps targets of the form armbe-* should just not be accepted at all?

(Or maybe armbe-* just doesn't mean 'ARM big endian' but something different?)

No it means, or should mean, big-endian. Since the "armbe" string is accepted by the top level config.sub file I guess that GAS should honor this version. Hence I am going to apply the patch below to fix this problem.


2004-07-15  Nick Clifton  <address@hidden>

        * configure.in: Accept armbe as a big-endian arm configuration.
        * configure: Regenerate.

RCS file: /cvs/src/src/gas/configure.in,v
retrieving revision 1.157
diff -c -3 -p -r1.157 configure.in
*** gas/configure.in    9 Jul 2004 12:32:32 -0000       1.157
--- gas/configure.in    15 Jul 2004 16:20:30 -0000
*************** changequote([,])dnl
*** 124,129 ****
--- 124,130 ----
      case ${cpu} in
        am33_2.0)               cpu_type=mn10300 endian=little ;;
        alpha*)         cpu_type=alpha ;;
+       arm*be|xscale*be|strongarm*be | \
        arm*b|xscale*b|strongarm*b) cpu_type=arm endian=big ;;
        arm*|xscale*|strongarm*)    cpu_type=arm endian=little ;;
        c4x*)           cpu_type=tic4x ;;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]