From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support
Date: Mon, 24 Aug 2009 14:49:14 +0200 [thread overview]
Message-ID: <20090824144914.5ab6c010@marrow.netinsight.se> (raw)
In-Reply-To: <20090824120120.99ECB833DBD2@gemini.denx.de>
On Mon, 24 Aug 2009 14:01:20 +0200
Wolfgang Denk <wd@denx.de> wrote:
> Please re-run the tests with
>
> $ USE_PRIVATE_LIBGCC=yes
> $ export USE_PRIVATE_LIBGCC
> $ make mrproper
> $ make ..._config
> $ make all
>
> and with
>
> $ unset USE_PRIVATE_LIBGCC
> $ make mrproper
> $ make ..._config
> $ make all
Same result both ways.
> > I'll send an updated version of the patch, but it can't go in until
> > mach-types.h has been updated at least. It's very similar to sheevaplug
> > though, but uses 64-bit vsnprintf since it needs UBIFS support. I guess
> > the nand_bbt problem is a similar issue.
>
> Again, guesses are simply not good enough to spend any efforts. We
> need clear, reliable facts.
Well, since I can't say what's causing the problem, it's a guess.
The hard facts are that the printf issue goes away if I compile without
CONFIG_SYS_64BIT_VSPRINTF, but the nand_bbt problem is always there.
I've tried looking at the disassembled source code, in particular of
the number() function and the calls of it in vsprintf.c, but I can't
easily spot where it goes wrong.
// Simon
next prev parent reply other threads:[~2009-08-24 12:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 11:17 [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support Wolfgang Denk
2009-08-17 13:00 ` Tom
2009-08-17 13:25 ` Wolfgang Denk
2009-08-17 15:26 ` Dirk Behme
2009-08-17 19:43 ` ksi at koi8.net
2009-08-17 20:17 ` Magnus Lilja
2009-08-17 20:27 ` Wolfgang Denk
2009-08-18 17:08 ` Magnus Lilja
2009-08-18 21:18 ` Wolfgang Denk
2009-08-18 11:06 ` Gaye Abdoulaye Walsimou
2009-08-18 11:22 ` Wolfgang Denk
2009-08-20 15:27 ` Andrzej Wolski
2009-08-18 11:45 ` Gaye Abdoulaye Walsimou
2009-08-18 18:50 ` Tom
2009-08-18 21:19 ` Wolfgang Denk
2009-08-21 21:12 ` Wolfgang Denk
2009-08-24 8:59 ` Simon Kagstrom
2009-08-24 10:01 ` Wolfgang Denk
2009-08-24 11:28 ` Prafulla Wadaskar
2009-08-24 11:56 ` Wolfgang Denk
2009-08-24 12:41 ` Prafulla Wadaskar
2009-08-24 12:59 ` Simon Kagstrom
2009-08-24 13:05 ` Wolfgang Denk
2009-08-24 11:38 ` Simon Kagstrom
2009-08-24 12:01 ` Wolfgang Denk
2009-08-24 12:49 ` Simon Kagstrom [this message]
2009-08-25 7:12 ` Simon Kagstrom
2009-09-04 20:05 ` Wolfgang Denk
2009-09-07 6:23 ` Simon Kagstrom
2009-09-07 8:59 ` Prafulla Wadaskar
2009-09-07 9:15 ` Simon Kagstrom
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=20090824144914.5ab6c010@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.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