From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] EABI 4.2
Date: Mon, 19 Apr 2010 13:07:45 +0200 [thread overview]
Message-ID: <m2ochf7la6.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4BCA2BA5.7030101@bumblecow.com> (Tom Rix's message of "Sat, 17 Apr 2010 16:44:05 -0500")
Hi Tom,
> Wolfgang Denk wrote:
>> Dear Tom,
>>
>> In message <20100317084833.364b27fa@marrow.netinsight.se> Simon Kagstrom wrote:
>>> (Sorry if this has already been taken up, I've not been following the
>>> discussion closely)
>>>
>>> On Thu, 11 Mar 2010 11:11:09 +0100
>>> "Martin Krause" <Martin.Krause@tqs.de> wrote:
>>>
>>>>>> Does this mean, my toolchain is broken? I use ELDK4.2 for ARM.
>>>>> I belive so, how many bytes is in dirent.namelen? alloca can not
>>>> I compiled the original code with VLA with ELDK4.1 and there
>>>> everything works. And also the '__builtin_alloca' Version works
>>>> with ELDK4.1.
>>> I had a similar problem a few months ago, which turned out to be a
>>> stack alignment issue:
>>>
>>> http://www.mail-archive.com/u-boot at lists.denx.de/msg23202.html
>>>
>>> the behavior was pretty similar, with code built with some compilers
>>> working (by chance) and some others breaking.
>>>
>>> (The patch above is in U-boot since november something I think)
>>
>> Is there any chance to have this fixed for all ARM variants during
>> this release cycle?
>>
>
> Yes. I will take this up.
> Please send me some instruction on how to get just the eldk4.2 toolchain.
ELDK4.2 is "atomic", i.e. you have to do a regular install to get the
toolchain[1].
Cheers
Detlev
[1] http://www.denx.de/wiki/view/DULG/ELDKAvailability
--
The proprietary-Unix players proved so ponderous, so blind, and so inept at
marketing that Microsoft was able to grab away a large part of their market
with the shockingly inferior technology of its Windows operating system.
-- "A Brief History of Hackerdom" by Eric Steven Raymond
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-04-19 11:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c166aa9f1003100750x40bdcef5vd41aed0b9036961a@mail.gmail.com>
2010-03-10 16:20 ` [U-Boot] EABI 4.2 Martin Krause
2010-03-10 16:35 ` Joakim Tjernlund
2010-03-10 16:52 ` Martin Krause
2010-03-10 17:29 ` Joakim Tjernlund
2010-03-11 10:11 ` Martin Krause
2010-03-11 16:27 ` Praveen G K
2010-03-12 9:04 ` Detlev Zundel
2010-03-12 16:12 ` Praveen G K
2010-03-16 18:50 ` Praveen G K
2010-03-16 22:18 ` Alessandro Rubini
2010-03-17 7:48 ` Simon Kagstrom
2010-03-17 14:53 ` Praveen G K
2010-03-17 15:12 ` Simon Kagstrom
2010-03-21 17:04 ` Wolfgang Denk
2010-04-09 21:07 ` Wolfgang Denk
2010-04-17 21:44 ` Tom Rix
2010-04-19 11:07 ` Detlev Zundel [this message]
[not found] <fe7c83ac1003091131g51889459p5e094e5cb74055db@mail.gmail.com>
2010-03-09 19:34 ` [U-Boot] Fwd: " Praveen G K
2010-03-09 19:34 ` [U-Boot] " Praveen G K
2010-03-10 11:09 ` Martin Krause
2010-03-10 14:44 ` Praveen G K
2010-03-10 15:20 ` Martin Krause
2010-03-10 15:43 ` Detlev Zundel
2010-03-10 16:23 ` Martin Krause
2010-03-10 15:42 ` Wolfgang Denk
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=m2ochf7la6.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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