[#4014] build failure in mach-common/lock.S:177
Submitted By: Mike Frysinger
Open Date
2008-04-06 15:34:58 Close Date
2008-04-09 16:52:57
Priority:
Medium Assignee:
Mike Frysinger
Status:
Closed Fixed In Release:
N/A
Found In Release:
N/A Release:
Category:
N/A Board:
N/A
Processor:
N/A Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Fixed
Uboot version or rev.:
Toolchain version or rev.:
App binary format:
N/A
Summary: build failure in mach-common/lock.S:177
Details:
mach-common/lock.S in the kernel has this line:
R2 = 0xFFFFFF87 (X);
which causes a build failure:
arch/blackfin/mach-common/lock.S: Assembler messages:
arch/blackfin/mach-common/lock.S:177: Error: Immediate value out of range. Input text was ).
Follow-ups
--- Javier Herrero 2008-04-06 16:26:39
I can not reproduce the error for H8606, BF532, with current trunk uClinux-dist
and with trunk toolchain at revision 2220 (last I've updated...):
AS arch/blackfin/mach-common/cacheinit.o
AS arch/blackfin/mach-common/entry.o
AS arch/blackfin/mach-common/interrupt.o
AS arch/blackfin/mach-common/lock.o
CC arch/blackfin/mach-common/irqpanic.o
CC arch/blackfin/mach-common/arch_checks.o
CC arch/blackfin/mach-common/ints-priority.o
Seems to assemble lock.S without problem.
--- Mike Frysinger 2008-04-09 16:52:56
the build failure seems to only occur on 64bit systems. probably because after
the change to 'long long' for scanned in values, doing something like:
R2 = 0xFFFFFF87 (X);
will be scanned in as a large unsigned quantity rather than a negative value.
if you want a negative value, then write something like "-121" or
"-0x79". dont max out the leading signed bits yourself.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
No Files Were Found