------- Additional Comments From mcvick_e at iname dot com  2005-08-24 00:20 
-------
Unfortunately this still appears to be some sort of bug.  The solution given 
with the -mstrict-align worked for the test case, but in the specific case 
here, still fails.  Attached is the output of the link command given.  The 
compiler invocation for all of the associated files that make the libraries, 
and object files all contain the -mstrict-align.

See the text below...


(1)> ppcg++ -gstabs+ -O1 -fno-guess-branch-probability -mcpu=603e -mtune=603e -
mstrict-align -nostdlib -DGH_COMPAT -DAVOID_EMPTY_CLASSES -DSVRT_TRACE -fno-use-
cxa-atexit -fcheck-new -fno-rtti -fno-exceptions -Wabi -
Wextra /export/GNU_port/MM.1/lib/sac/begin.o /export/GNU_port/MM.1/lib/sac/sysin
it.o /export/GNU_port/MM.1/lib/sac/prepccfg.o /export/GNU_port/MM.1/lib/sac/psos
cfg.o /export/GNU_port/MM.1/lib/sac/drv_conf.o  --no-undefined -Bstatic --warn-
section-align --demangle --warn-once --warn-common --sort-common -T sac.cmd -
L /export/GNU_port/MM.1/lib -L /export/GNU_port/MM.1/lbcs/lib \
-o /export/GNU_port/MM.1/bins/sac.x

-------------------------------------------------------------------

(2)> ppcobjdump -C -S sac.x | grep sth | less

  494108:       b3 43 00 18     sth     r26,24(r3)
  49410c:       b3 23 00 1a     sth     r25,26(r3)
  494110:       b3 03 00 1c     sth     r24,28(r3)
  494c0c:       b0 01 00 21     sth     r0,33(r1)       <-- Still ODD alignment
  4954a0:       b1 3a 30 ec     sth     r9,12524(r26)
  4956ac:       b1 23 00 04     sth     r9,4(r3)
  4957d4:       b0 03 00 a4     sth     r0,164(r3)
  4959a8:       b1 23 00 00     sth     r9,0(r3)
  495bac:       b0 03 00 a4     sth     r0,164(r3)
  495ed0:       b1 2a 30 e0     sth     r9,12512(r10)

(3)>


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23539

Reply via email to