public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] [STATUS] for 04/21 release
Date: Mon, 16 Apr 2012 17:04:32 +0200	[thread overview]
Message-ID: <4F8C3500.3070500@aribaud.net> (raw)

Hi all,

I have just done a ./MAKEALL arm with the Mentor Graphics / CodeSourcery 
toochain release 2011.09-69, and the results are:

- 277 targets built
- 32 targets with warnings
- 3 targets with errors

Of the 61 warnings generated, there are only two sorts:

- 48 'warning: 
/opt/arm-2011.09/bin/../lib/gcc/arm-none-eabi/4.6.1/libgcc.a(xxxxxx.o) 
uses variable-size enums yet the output is to use 32-bit enums; use of 
enum values across objects may fail'

- 13 'warning: variable 'XXXXX' set but not used 
[-Wunused-but-set-variable]'

Neither of which seem too worrisome to me (although of course the 
defined-but-unused variables should be cleaned up).

The 3 errors are of one sort:

- 'internal compiler error: in decode_addr_const, at varasm.c:2635'. :)

Considering the three boards involved (omap4_panda, omap4_sdp4430 and 
omap5_evm) build correctly (with only 'variable-size enum' warnings) 
using the CodeSourcery 2011q1 toolchain, I take the errors to be faults 
in the toolchain, not the U-Boot code.

As I have not been able to follow the list closely these last days, 
please let me know of any pending issue regarding ARM and the 04/21 release.

Amicalement,
-- 
Albert.

                 reply	other threads:[~2012-04-16 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F8C3500.3070500@aribaud.net \
    --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