From: Dave Martin <Dave.Martin@arm.com>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: Lino Sanfilippo <lsanfil@marvell.com>,
linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"
Date: Tue, 24 Mar 2015 12:07:39 +0000 [thread overview]
Message-ID: <20150324120733.GA3579@e103592.cambridge.arm.com> (raw)
In-Reply-To: <550E132A.7050304@gmx.de>
On Sun, Mar 22, 2015 at 01:56:10AM +0100, Lino Sanfilippo wrote:
> On 06.03.2015 19:20, Lino Sanfilippo wrote:
> >
> >>>
> >>
> >> Ok, I got a link to the source now. It can be found here:
> >>
> >> http://tp-lab200/release/gcc/temp/internal/2010q4-113-4.4.5/marvell-gcc.src-2010q4-113.tar.bz2
> >>
> >
> >
> > Sigh. Just realized that the url is not accessible. Will check that on
> > monday.
> >
> > Lino
> >
>
> Hello Dave,
>
> sorry for my late reply. But I was a few days out of office and had to
> contact some people which are not in my departement. The outcome is:
> there is no public repository in which the source code of that special
> (buggy) toolchain is available any more. There are newer versions
> already, but even for those the source code is only accessible for
> customers (thats what I was told). However the responsible developer
(GPL?)
> could confirm that the wrong alignment I initially reported is indeed a
> bug in the toolchain which now is fixed in the newer versions.
> I really would have liked to send you the source, but unfortunately I
> cant. However thanks again for all your help.
Never mind -- hopefully this issue was caused by something that got
fixed upstream meanwhile, or that never went upstream in the first
place. Debugging legacy vendor toolchain forks isn't a very interesting
pursuit...
We can revisit the issue if it comes up again, but I've not heard
of any other instances of this type of issue so far.
Cheers
---Dave
prev parent reply other threads:[~2015-03-24 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 10:01 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
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 [this message]
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=20150324120733.GA3579@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--cc=LinoSanfilippo@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lsanfil@marvell.com \
/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
Powered by JetHome