Just figured out it was the "-mstrict-align" switch; removing it
does what I want, and in this case it also makes the asm output (and
I assume the resulting object code too) roughly 30% smaller. Is there
a good reason for keeping it? Is it required for internal EPICS
reasons, and if so can we at least turn it off in user code, e.g.
device support? Or is it perhaps a local SLAC thing...
Mike
----------------------
.align 2
.type copy4,@function
copy4:
mr 0,5
cmpwi 1,0,0
addi 5,5,-1
bclr 4,5
.L16:
lwz 0,0(3)
addi 3,3,4
mr 9,5
cmpwi 1,9,0
addi 5,5,-1
stw 0,0(4)
addi 4,4,4
bc 12,5,.L16
blr
.Lfe4:
.size copy4,.Lfe4-copy4
----------------------
- Replies:
- RE: PPC compiler splits up ints & shorts? Lawrence T. Hoff
- Navigate by Date:
- Prev:
PPC compiler splits up ints & shorts? Laznovsky, Michael
- Next:
RE: PPC compiler splits up ints & shorts? Lawrence T. Hoff
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: PPC compiler splits up ints & shorts? Dirk Zimoch
- Next:
RE: PPC compiler splits up ints & shorts? Lawrence T. Hoff
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|