From: Meelis Roos <mroos@linux.ee>
To: David Miller <davem@davemloft.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: unaligned accesses in SLAB etc.
Date: Fri, 17 Oct 2014 00:38:20 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.11.1410170012130.19924@adalberg.ut.ee> (raw)
In-Reply-To: <20141015.231154.1804074463934900124.davem@davemloft.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 936 bytes --]
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@linux.ee)
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 15992 bytes --]
[-- Attachment #3: Type: APPLICATION/octet-stream, Size: 15472 bytes --]
next prev parent reply other threads:[~2014-10-16 21:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 2:15 unaligned accesses in SLAB etc David Miller
2014-10-12 17:20 ` David Miller
2014-10-13 20:22 ` mroos
2014-10-13 23:52 ` Joonsoo Kim
2014-10-14 0:04 ` David Miller
2014-10-14 0:14 ` Joonsoo Kim
2014-10-14 21:19 ` mroos
2014-10-14 21:32 ` David Miller
2014-10-15 8:04 ` Meelis Roos
2014-10-15 18:36 ` David Miller
2014-10-15 20:11 ` Meelis Roos
2014-10-16 3:11 ` David Miller
2014-10-16 7:22 ` Meelis Roos
2014-10-16 20:11 ` Meelis Roos
2014-10-16 20:18 ` David Miller
2014-10-16 21:38 ` Meelis Roos [this message]
2014-10-19 4:32 ` David Miller
2014-10-19 7:07 ` Meelis Roos
2014-10-20 18:57 ` David Miller
2014-10-22 20:39 ` David Miller
2014-10-22 23:22 ` Meelis Roos
2014-10-23 17:02 ` David Miller
2014-10-23 21:22 ` David Miller
2014-10-24 4:54 ` Sam Ravnborg
2014-10-24 16:53 ` David Miller
2014-10-24 7:49 ` Meelis Roos
2014-10-24 16:45 ` David Miller
2014-10-16 7:02 ` Meelis Roos
2014-10-16 20:07 ` David Miller
2014-10-16 20:16 ` Meelis Roos
2014-10-16 20:20 ` David Miller
2014-10-16 20:50 ` David Miller
2014-10-17 11:12 ` Meelis Roos
2014-10-18 17:59 ` David Miller
2014-10-18 18:23 ` David Miller
2014-10-19 12:31 ` Meelis Roos
2014-10-19 17:12 ` Meelis Roos
2014-10-19 17:18 ` David Miller
2014-10-19 15:32 ` Sam Ravnborg
2014-10-19 17:27 ` David Miller
2014-10-19 19:55 ` Sam Ravnborg
2014-10-16 20:20 ` Meelis Roos
2014-10-16 20:40 ` Meelis Roos
2014-10-12 17:22 ` Joonsoo Kim
2014-10-12 17:30 ` David Miller
2014-10-12 17:43 ` Joonsoo Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.11.1410170012130.19924@adalberg.ut.ee \
--to=mroos@linux.ee \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).