From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] analyze/change assembly code
Date: Tue, 20 Nov 2012 14:40:03 +0100 [thread overview]
Message-ID: <20121120144003.27ac545d@lilith> (raw)
In-Reply-To: <201211201426.15738.marex@denx.de>
Hi Marek, Gerlando,
On Tue, 20 Nov 2012 14:26:15 +0100, Marek Vasut <marex@denx.de> wrote:
> > What do you mean it didn't behave properly???? How's that even possible?
>
> The Linaro toolchain had broken libgcc and u-boot pulls in components from this
> libgcc ... thus the breakage.
Marek: I don't know if that is supposed to be a case where Linaro is
supposed to fail, but FWIW, a versatileqemu build performed with the
Linaro ARM gcc version from Ubuntu 12.04 would fail to run whereas built
with the Linaro ARM gcc from Ubuntu 12.10 -- 4.7.2 (Ubuntu/Linaro
4.7.2-1ubuntu1) -- it does work. So maybe Linaro fixed their act.
> > A compiler which doesn't translate to assembly and from assembly to
> > binary is by definition a _BROKEN_ compiler
Gerlando, you may have to revise this definition: I think LLVM does
not necessarily translate through assembly language, at least, not
through the target's assembly language, and LLVM assembly language may
count as 'intermediate representation' rather than true 'assembly
language'.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-11-20 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 11:08 [U-Boot] analyze/change assembly code Gerlando Falauto
2012-11-10 11:25 ` Albert ARIBAUD
2012-11-19 6:23 ` Gerlando Falauto
2012-11-20 8:54 ` Marek Vasut
2012-11-20 9:43 ` Gerlando Falauto
2012-11-20 13:26 ` Marek Vasut
2012-11-20 13:40 ` Albert ARIBAUD [this message]
2012-11-20 13:48 ` Gerlando Falauto
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=20121120144003.27ac545d@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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