From: lsanfil@marvell.com (Lino Sanfilippo)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"
Date: Thu, 5 Mar 2015 14:20:43 +0100 [thread overview]
Message-ID: <54F8582B.80703@marvell.com> (raw)
In-Reply-To: <20150305122606.GC3612@e103592.cambridge.arm.com>
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
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.
Dave, I thank you very much for your help and efforts to clarify that
this is actually not a bug in the kernel.
Thx,
Lino
next prev parent reply other threads:[~2015-03-05 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 10:01 [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section" Lino Sanfilippo
2015-03-02 10:01 ` [RFC PATCH 1/1] ARM: Ensure correct structure alignment when using " Lino Sanfilippo
2015-03-03 14:41 ` [RFC PATCH 0/1] Wrong structure alignment due to " Dave Martin
2015-03-04 11:40 ` sanfilippo
2015-03-04 14:35 ` Dave Martin
2015-03-04 16:29 ` Lino Sanfilippo
2015-03-05 12:26 ` Dave Martin
2015-03-05 13:20 ` Lino Sanfilippo [this message]
2015-03-05 13:47 ` Dave Martin
2015-03-05 15:32 ` Lino Sanfilippo
2015-03-05 17:33 ` Dave Martin
2015-03-06 14:02 ` Lino Sanfilippo
2015-03-06 18:20 ` Lino Sanfilippo
2015-03-22 0:56 ` Lino Sanfilippo
2015-03-24 12:07 ` Dave Martin
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=54F8582B.80703@marvell.com \
--to=lsanfil@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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).