U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Missing __udivdi3 for ARM
Date: Sun, 02 Aug 2009 09:18:17 +0200	[thread overview]
Message-ID: <4A753DB9.6080508@googlemail.com> (raw)
In-Reply-To: <20090801200127.B87B3832E416@gemini.denx.de>

Dear Wolfgang,

Wolfgang Denk wrote:
> Dear "J.C. Wren",
> 
> In message <17434f2e0908011243y666d2d40if6fdfd8a5c00c7c5@mail.gmail.com> you wrote:
>> I thought the idea was to move u-boot away from libgcc dependencies.  Or did
>> I misread that?  I know that a previous problem I commented on was solved by
>> adding a __xxxxx.S function the u-boot library.
> 
> In a perfect world the GCC provided libgcc.a would be "just working"
> and we did not have to bother about all that.
> 
> But libgcc.a fo ARM is obviously not perfect, and causes problems. So
> Jean-Christophe suggested to use the  alternative  implementation  he
> wanted to copy from the Linux code - which again is supposed to allow
> to use the code in question without changes.

Just to get an idea what has to be done for this:

Do we talk about

http://lists.denx.de/pipermail/u-boot/2009-June/054627.html

without the changes to top level

Makefile
arm_config.mk

?

That is, updating that patch and removing the Makefile and 
arm_config.mk changes would be what we want?

Best regards

Dirk

  reply	other threads:[~2009-08-02  7:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 21:40 [U-Boot] Missing __udivdi3 for ARM J.C. Wren
2009-07-31 22:36 ` Wolfgang Denk
2009-08-01 13:26 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-01 14:40   ` Wolfgang Denk
2009-08-01 16:14     ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-01 19:57       ` Wolfgang Denk
2009-08-01 19:43     ` J.C. Wren
2009-08-01 20:01       ` Wolfgang Denk
2009-08-02  7:18         ` Dirk Behme [this message]
2009-08-02  8:27           ` 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=4A753DB9.6080508@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --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