[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150305134733.GE3612@e103592.cambridge.arm.com>
Date: Thu, 5 Mar 2015 13:47:33 +0000
From: Dave Martin <Dave.Martin@....com>
To: Lino Sanfilippo <lsanfil@...vell.com>
Cc: LinoSanfilippo@....de, linux@....linux.org.uk,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler
attribute "section"
On Thu, Mar 05, 2015 at 02:20:43PM +0100, Lino Sanfilippo wrote:
> On 05.03.2015 13:26, Dave Martin wrote:
>
> >>
> >>So this is indeed a compiler bug, right?
> >
> >It certainly looks like the compiler is causing the issue somehow.
> >
> >Whether this is a bug, a bug-like feature, a configuration issue,
> >or a combination of these is not clear.
> >
> >If you know where to find the toolchain source, it might be worth
> >taking a look.
>
> The toolchain can be found here:
> http://www.plugcomputer.org/405/us/gplugd/tool-chain/arm-marvell-linux-gnueabi.tar.bz2
Source code? That just looks like binaries to me.
> But since it turns out to be a compiler issue I dont know if its
> worth to be investigated further. I think the best solution to avoid
> that structure alignment problem is to simply use another toolchain.
Maybe not. Could be worth revisiting if other people report the
same problem -- a build-time check that
> Dave, I thank you very much for your help and efforts to clarify
> that this is actually not a bug in the kernel.
No probs. I have wondered whether it's really valid to assume
that the linker can paste sections from different objects into a valid
array like this.
There are other things that already work this way though -- such
as the way .init_array/.fini_array are created when building
a shared library.
Cheers
---Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists