[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.11.1410170012130.19924@adalberg.ut.ee>
Date: Fri, 17 Oct 2014 00:38:20 +0300 (EEST)
From: Meelis Roos <mroos@...ux.ee>
To: David Miller <davem@...emloft.net>
cc: Linux Kernel list <linux-kernel@...r.kernel.org>,
sparclinux@...r.kernel.org
Subject: Re: unaligned accesses in SLAB etc.
Removed non-sparc64 people from CC to not spam them. Kept the lists
though.
> Do you happen to have both gcc-4.9 and a previously working compiler
> on these systems? If you do, we can build a kernel with gcc-4.9 and
> then selectively compile certain failes with the older working
> compiler to narrow down what compiles into something non-working with
> gcc-4.9
>
> I would start with the following files:
>
> arch/sparc/mm/init_64.c
> arch/sparc/mm/tlb.c
> arch/sparc/mm/tsb.c
> arch/sparc/mm/fault_64.c
>
> And failing that, go for various files under arch/sparc/kernel/ such as:
>
> arch/sparc/kernel/process_64.c
> arch/sparc/kernel/smp_64.c
> arch/sparc/kernel/sys_sparc_64.c
> arch/sparc/kernel/sys_sparc32.c
> arch/sparc/kernel/traps_64.c
arch/sparc/kernel/setup_64.c is the only culprit.
Attached are 2 versions of the object file as of v3.17-rc1-22-g480cadc
that I tested.
--
Meelis Roos (mroos@...ux.ee)
Download attachment "setup_64.o_gcc46" of type "APPLICATION/octet-stream" (15992 bytes)
Download attachment "setup_64.o_gcc49" of type "APPLICATION/octet-stream" (15472 bytes)
Powered by blists - more mailing lists