Re: powerpc/ppc64: Allow allmodconfig to build (finally !)
From: Guenter Roeck <linux@roeck-us.net>
Date: 2014-05-14 05:17:01
On 05/13/2014 08:34 PM, Stephen Rothwell wrote:
Hi Guenter, On Tue, 13 May 2014 10:17:49 -0700 Guenter Roeck [off-list ref] wrote:quoted
On Tue, May 13, 2014 at 07:16:41PM +1000, Benjamin Herrenschmidt wrote:quoted
On Mon, 2014-05-12 at 17:28 -0700, Guenter Roeck wrote:quoted
After applying this patch, I get arch/powerpc/kernel/exceptions-64s.S:269: Error: operand out of range (0x000000000000814c is not between 0xffffffffffff8000 and 0x0000000000007ffc) arch/powerpc/kernel/exceptions-64s.S:729: Error: operand out of range (0x000000000000814c is not between 0xffffffffffff8000 and 0x0000000000007ffc) with powerpc:defconfig, powerpc:allmodconfig, powerpc:cell_defconfig, and powerpc:maple_defconfig. This is on top of v3.15-rc5. Any idea what is going on ? Compiler is powerpc64-poky-linux-gcc (GCC) 4.7.2 (from poky 1.4.0-1).Interesting... works with all my test configs using 4.7.3... I don't have my tree at hand right now, I'll check what that means tomorrow see if I can find a workaround.It works for me with gcc 4.8.2 (build from yocto 1.6.0). Is asking people to use gcc 4.7.3 or later acceptable ?OK, this appears to be an assembler bug. $ cat test.s .text x: .pushsection b, "a" beq y .popsection .=0x80000 y: $ /opt/cross/gcc-4.6.3-nolibc/powerpc64-linux/bin/powerpc64-linux-as --version GNU assembler (GNU Binutils) 2.22 This assembler was configured for a target of `powerpc64-linux'. $ /opt/cross/gcc-4.6.3-nolibc/powerpc64-linux/bin/powerpc64-linux-as -o test.o test.s test.s: Assembler messages: test.s:4: Error: operand out of range (0x0000000000080000 is not between 0xffffffffffff8000 and 0x0000000000007ffc) $ /opt/cross/gcc-4.8.1-nolibc/powerpc64-linux/bin/powerpc64-linux-as --version GNU assembler (GNU Binutils) 2.23.52.20130512 This assembler was configured for a target of `powerpc64-linux'. $ /opt/cross/gcc-4.8.1-nolibc/powerpc64-linux/bin/powerpc64-linux-as -o test.o test.s (no error) Alan, can you shed light on when it was fixed?
Hi Stephen, any idea what might cause this one, by any chance ? arch/powerpc/kernel/built-in.o: In function `exc_debug_crit_book3e': (.text+0x165ee): relocation truncated to fit: R_PPC64_ADDR16_HI against symbol `interrupt_base_book3e' defined in .text section in arch/powerpc/kernel/built-in.o arch/powerpc/kernel/built-in.o: In function `exc_debug_crit_book3e': (.text+0x16602): relocation truncated to fit: R_PPC64_ADDR16_HI against symbol `interrupt_end_book3e' defined in .text section in arch/powerpc/kernel/built-in.o arch/powerpc/kernel/built-in.o: In function `exc_debug_debug_book3e': I see this if I try to build powerpc:ppc64e_defconfig or powerpc:chroma_defconfig with gcc 4.8.2 and binutils 2.24. Thanks, Guenter