What steps will reproduce the problem?
Run the following through the assembler:
LPC176:
add r12, pc, r12
flds s28, [r12]
flds s29, [r0, #+20]
fsts s29, [sp, #+32]
flds s29, [r0, #+28]
fsts s29, [sp, #+24]
flds s29, [r0, #+16]
fsts s29, [sp, #+20]
flds s29, [r0, #+4]
flds s30, [r0, #+8]
flds s31, [r0, #+24]
fsts s31, [sp, #+12]
flds s31, [r0, #+12]
fsts s31, [sp]
flds s31, [r0, #+32]
fsts s26, [r2, #+36]
flds s26, [r3, #+104]
fmuls s24, s26, s24
e.g. /usr/local/bin/arm-apple-darwin-as -arch arm -force_cpusubtype_ALL -o
foo.o foo.s
This produces the following errors:
foo.s:12:parse error, expecting `OPRD_REG_S'
foo.s:13:Spurious digit 0.
foo.s:13:Rest of line ignored. 1st junk character valued 91 ([).
foo.s:13:parse error, expecting `OPRD_REG_S'
foo.s:14:Spurious digit 0.
foo.s:14:Rest of line ignored. 1st junk character valued 91 ([).
foo.s:14:parse error, expecting `OPRD_REG_S'
foo.s:15:Spurious digit 0.
foo.s:15:Rest of line ignored. 1st junk character valued 91 ([).
foo.s:15:parse error, expecting `OPRD_REG_S'
foo.s:16:Spurious digit 0.
foo.s:16:Rest of line ignored. 1st junk character valued 91 ([).
foo.s:16:parse error, expecting `OPRD_REG_S'
foo.s:17:Spurious digit 0.
foo.s:17:Rest of line ignored. 1st junk character valued 91 ([).
What is the expected output? What do you see instead?
The parse errors prevent the assembler from producing an object file
What version of the product are you using? On what operating system?
/usr/local/bin/arm-apple-darwin-gcc -v
Using built-in specs.
Target: arm-apple-darwin
Configured with: ../llvm-gcc-4.0-iphone/configure
--enable-llvm=/Users/mccreary/iPhone/llvm-svn
--enable-languages=c,c++,objc,obj-c++ --target=arm-apple-darwin
--enable-sjlj-exceptions
--with-heavenly=/usr/local/share/Heavenly1A543a.UserBundle
--with-as=/usr/local/bin/arm-apple-darwin-as
--with-ld=/usr/local/bin/arm-apple-darwin-ldThread model: posixgcc version
4.0.1 (Apple Computer, Inc. build 5449)(LLVM build 2.0-svn-iphone-dev-0.3-svn)
The host OS is MacOS X 10.4.8
Please provide any additional information below.
Original issue reported on code.google.com by sean.mcc...@gmail.com on 12 Sep 2007 at 11:38
Original issue reported on code.google.com by
sean.mcc...@gmail.com
on 12 Sep 2007 at 11:38