public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] Status for 2012.03
Date: Fri, 30 Mar 2012 16:29:12 +0200	[thread overview]
Message-ID: <201203301629.12694.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ25W_bvkg_K_q4=n0WJtTAM386TqMA=Ef=An+tY=HX4sA@mail.gmail.com>

Dear Simon Glass,

> Hi Marek,
> 
> On Fri, Mar 30, 2012 at 6:52 AM, Marek Vasut <marex@denx.de> wrote:
> > Dear Simon Glass,
> > 
> >> +Marek
> >> 
> >> Hi Albert,
> >> 
> >> On Fri, Mar 30, 2012 at 12:08 AM, Albert ARIBAUD
> >> 
> >> <albert.u.boot@aribaud.net> wrote:
> >> > Le 27/03/2012 22:18, Albert ARIBAUD a ?crit :
> >> >> Hi all,
> >> >> 
> >> >> 
> >> >> I have been away from the list quite a few days, and will have a very
> >> >> tricky time catching up, so with my apologies, I ask people who need
> >> >> me to apply patches or pull requests for the upcoming release to
> >> >> please send me a private e-mail and point me to the list message
> >> >> that I should be acting upon.
> >> > 
> >> > FWIW, ./MAKEALL arm on current u-boot-arm/master with CS toolchain
> >> > 2010q1 builds 277 boards, of which none has errors and 167 have
> >> > warnings.
> >> > 
> >> > The total count of warnings is 248, distributed as:
> >> > 
> >> > 4       post.c:503: warning: #warning "Not implemented yet"
> >> > 
> >> > 79      mmc.c:132: warning: no return statement in function returning
> >> > non-void
> >> > 
> >> > 165     ohci-hcd.c:{1307,1310,1313}: warning: dereferencing pointer
> >> > 'pretmp.NNN' does break strict-aliasing rules
> >> 
> >> I did create a patch for this - it is marked delegated to Marek.
> >> 
> >> http://patchwork.ozlabs.org/patch/134600/
> > 
> > And stupid maintainer didn't look into it ... bad, bad maintainer. Accept
> > my apology. But wasn't it decided with Mike that this was indeed a
> > toolchain issue and not all toolchains choke on it?
> :
> :-)
> 
> Yes. It does feel like a broken toolchain (I felt that the original
> code should be warning free, even when I wrote my patch) but it seems
> that Albert gets this warning as well. Maybe we should fix it?

I don't see this with ELDK 4.2 or 5.0 or 5.1 ;-)

Maybe fundamental rewrite of that code might help instead of adding bandaids ;-)

> >> > (the last one is actually 3 * 51 warnings)
> >> > 
> >> > The first one is obvious and should be dealt with, but I consider it
> >> > not to be a blocker, for only 4 boards.
> >> > 
> >> > The second one seems straightforward to fix today, if not already
> >> > submitted.
> >> > 
> >> > The third one may be an issue, but it could also be a zealous warning
> >> > from the specific CS toolchain version I am using. Anyway, it does not
> >> > seem ARM related as such.
> >> 
> >> Would be nice to get rid of it, but I think it is specific to some
> >> toolchains.
> >> 
> >> > Therefore I will issue the ARM pull request right away.
> >> > 
> >> > 
> >> > Amicalement,
> >> > --
> >> > Albert.
> >> > _______________________________________________
> >> > U-Boot mailing list
> >> > U-Boot at lists.denx.de
> >> > http://lists.denx.de/mailman/listinfo/u-boot
> >> 
> >> Regards,
> >> Simon
> > 
> > Best regards,
> > Marek Vasut
> 
> Regards,
> Simon

  reply	other threads:[~2012-03-30 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 20:18 [U-Boot] [ARM] Status for 2012.03 Albert ARIBAUD
2012-03-30  6:23 ` Albert ARIBAUD
2012-03-30  7:08 ` Albert ARIBAUD
2012-03-30 13:16   ` Simon Glass
2012-03-30 13:52     ` Marek Vasut
2012-03-30 13:56       ` Simon Glass
2012-03-30 14:29         ` Marek Vasut [this message]
2012-03-31  8:15           ` Simon Glass
2012-03-30 13:31   ` Valentin Longchamp
  -- strict thread matches above, loose matches on Subject: below --
2012-03-27 20:18 Albert ARIBAUD

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=201203301629.12694.marex@denx.de \
    --to=marex@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