On Thu, 12 Jun 2008 15:03:35 +0930 Alan Modra [EMAIL PROTECTED] wrote:
On Thu, Jun 12, 2008 at 11:38:19AM +1000, Paul Mackerras wrote:
Direct unconditional branches, including procedure calls, can only
reach +/- 32MB from the address of the branch on powerpc. So if the
image grows to more
* Stephen Rothwell [EMAIL PROTECTED] wrote:
It is, but you need to pass --relax to enable generation of the
trampolines.
So I tried this (added --relax to LDFLAGS_vmlinux if CONFIG FTRACE was
set) and got this;
/usr/bin/ld: --relax and -r may not be used together
So, I will
On Thu, 12 Jun 2008 17:05:05 +1000 Stephen Rothwell [EMAIL PROTECTED] wrote:
So, I will disable FTRACE on powerpc for now by removing HAVE_FTRACE from
being selected in arch/powerpc/Kconfig.
That got rid of the initial errors, but now it fails for relocations
on .memcmp and some others.
Next
On Thu, 2008-06-12 at 17:05 +1000, Stephen Rothwell wrote:
So I tried this (added --relax to LDFLAGS_vmlinux if CONFIG FTRACE was
set) and got this;
/usr/bin/ld: --relax and -r may not be used together
So, I will disable FTRACE on powerpc for now by removing HAVE_FTRACE
from
being
Hi Ingo,
On Thu, 12 Jun 2008 09:16:12 +0200 Ingo Molnar [EMAIL PROTECTED] wrote:
ugh, please do that hack only privately in your allyesconfig testing and
do not commit that change to linux-next!
See my other email, I have removed the ftrace disabling patch and
reverted one of Sam Ravnborg's
On Thu, Jun 12, 2008 at 05:05:05PM +1000, Stephen Rothwell wrote:
/usr/bin/ld: --relax and -r may not be used together
Can't you arrange so that --relax is only used on the final link? Of
course, if you have mashed all the input .text sections together with
ld -r, resulting in one monster .text
On Thu, Jun 12, 2008 at 05:24:03PM +1000, Stephen Rothwell wrote:
On Thu, 12 Jun 2008 17:05:05 +1000 Stephen Rothwell [EMAIL PROTECTED] wrote:
So, I will disable FTRACE on powerpc for now by removing HAVE_FTRACE from
being selected in arch/powerpc/Kconfig.
That got rid of the initial
Hi all,
Today's linux-next build (powerpc allyesconfig) failed like this:
vmlinux.o: In function `ipx_ioctl':
/scratch/sfr/next/net/ipx/af_ipx.c:1830: relocation truncated to fit:
R_PPC64_REL24 against symbol `._mcount' defined in .text section in vmlinux.o
(and lots more similar)
I am
Ingo Molnar writes:
could this be a tool chain limitation perhaps, or a gcc bug? Or does the
allyesconfig size go beyond some fundamental hardware limitation. (i
doubt it's the latter)
Direct unconditional branches, including procedure calls, can only
reach +/- 32MB from the address of the
On Thu, Jun 12, 2008 at 11:38:19AM +1000, Paul Mackerras wrote:
Direct unconditional branches, including procedure calls, can only
reach +/- 32MB from the address of the branch on powerpc. So if the
image grows to more than 32MB of text there is a problem unless the
linker is smart enough to
Hi Paul,
Today's linux-next tree build (powerpc ppc64_defconfig) failed like this:
UPD include/linux/compile.h
arch/powerpc/mm/built-in.o: In function `ht64_insert_pte':
hash_native_64.c:(.text+0x4756): undefined reference to `_PAGE_HPTE_SUB0'
I have reverted commit
On Tue, 2008-06-10 at 16:54 +1000, Stephen Rothwell wrote:
Hi Paul,
Today's linux-next tree build (powerpc ppc64_defconfig) failed like this:
UPD include/linux/compile.h
arch/powerpc/mm/built-in.o: In function `ht64_insert_pte':
hash_native_64.c:(.text+0x4756): undefined reference
12 matches
Mail list logo
