All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default
Date: Wed, 1 Jul 2015 23:21:44 +0200	[thread overview]
Message-ID: <20150701232144.600ee35a@lilith> (raw)
In-Reply-To: <20150416112144.3a6b4813@lilith>

On Thu, 16 Apr 2015 11:21:44 +0200, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> Hello Masahiro,
> 
> Your patch clashes with Pavel's already committed
> break-if-private-libgcc-and-thumb, causing many boards to fail building.
> 
> I am putting your patch in 'under review' state until I can have a look
> at what happens with private libgcc and thumb.

Hmm, even with the libgcc+thumb thing fixed, this patch still causes
quite a few target to fail:

- without the patch, buildman yields 503 1 12 / 516.
- With the patch, buildman yields 488 1 27 / 516.

Of these, 10 are aarch64 boards which now try to build a private libgcc
with some hardwired 32-bit mnemonics :

| arch/arm/lib/_ashldi3.S:21: Error: operand 1 should be an integer
register -- `subs r3,r2,#32' | arch/arm/lib/_ashldi3.S:22: Error: unknown mnemonic `rsb' -- `rsb ip,r2,#32' 
| arch/arm/lib/_ashldi3.S:23: Error: unknown mnemonic `movmi' -- `movmi r1,r1,lsl r2' 
| arch/arm/lib/_ashldi3.S:24: Error: unknown mnemonic `movpl' -- `movpl r1,r0,lsl r3' 
| arch/arm/lib/_ashldi3.S:25: Error: unknown mnemonic `orrmi' -- `orrmi r1,r1,r0,lsr ip' 
| arch/arm/lib/_ashldi3.S:26: Error: operand 1 should be an integer register -- `mov r0,r0,lsl r2' 
| arch/arm/lib/_ashldi3.S:27: Error: operand 1 should be an integer register -- `mov pc,lr' 

This should be fairly easy to fix by
 defaulting CONFIG_USE_PRIVATE_LIBGCC to 

The other 5 failures are snow, smdk5250, peach-pi, smdk5420, and
peach-pit, all of which show the same error:

> arch/arm/lib/lib.a(div0.o): In function `__div0': 
> arch/arm/lib/div0.c:13: undefined reference to `hang' 
> make[2]: *** [spl/u-boot-spl] Error 1 
> make[1]: *** [spl/u-boot-spl] Error 2 

That one is be a dependency on hang(). This function... hangs out... in
lib/hang.c, which according to lib/Makefile should be included in any
build, SPL or otherwise; but it appears lib/ is not built at all for
SPL, at least for these five targets.

Masahiro, can you have a look at e.g. snow (arm) and ls2085ardb
(aarch64) and see if you can update your patch to make sure these two
targets build? The other 13 should follow then.

> Amicalement,
> -- 
> Albert.

Amicalement,
-- 
Albert.

  reply	other threads:[~2015-07-01 21:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 12:37 [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default Masahiro Yamada
2015-04-16  9:21 ` Albert ARIBAUD
2015-07-01 21:21   ` Albert ARIBAUD [this message]
2015-07-01 21:40     ` Albert ARIBAUD
2015-07-02 12:21     ` Masahiro Yamada
2015-07-02 12:43       ` Albert ARIBAUD
2015-07-02 12:54         ` Masahiro Yamada
2015-07-02 13:03           ` Albert ARIBAUD
2015-07-01 21:42   ` [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default (re-send to the correct address) Albert ARIBAUD
2015-07-01 21:50     ` Wolfgang Denk
2015-07-01 22:04       ` Albert ARIBAUD
2015-07-01 23:39         ` Daniel Schwierzeck
2015-07-02  5:49           ` Albert ARIBAUD
2015-07-02  7:39           ` Wolfgang Denk
2015-07-02 12:40             ` Masahiro Yamada
2015-07-03  9:53               ` Wolfgang Denk
2015-07-02 12:46             ` Daniel Schwierzeck
2015-07-03  9:59               ` Wolfgang Denk
2015-07-02 12:18           ` Masahiro Yamada
2015-07-02 12:29             ` Masahiro Yamada
2015-07-03  9:29             ` Wolfgang Denk
2015-07-02  7:34         ` Wolfgang Denk
2015-07-02 12:12           ` Masahiro Yamada
2015-07-03  9:25             ` 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=20150701232144.600ee35a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.