All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Bug with newer GCC
Date: Fri, 01 Feb 2013 22:36:29 +0100	[thread overview]
Message-ID: <20130201213629.AD73B20055E@gemini.denx.de> (raw)
In-Reply-To: <E70AF999396FDF4EAE40E195B847096109F5D6FD@SRVEXCH-2K10.CADCON.INTERN>

Dear Sebastian,

In message <E70AF999396FDF4EAE40E195B847096109F5D6FD@SRVEXCH-2K10.CADCON.INTERN> you wrote:
> 
> We use a custom board configuration for our custom hardware.
> I can send parts of it, if needed.

Thanks, but no.  Parts are of no use to us.  Basicly you have to
options: have your code merged into mainline (to do that you have to
submit a complete set of patches here on the mailing list), or
maintain your out-of-tree port yourself (in which case David
Woodhouse's statement applies, see
http://article.gmane.org/gmane.linux.kernel.embedded/3534).

> We are currently using v2012.10.

This works fine for the mainline code.

> The toolchain is OSELAS.2012.12.0 (http://www.pengutronix.de/oselas/toolchain).

So eother it's an issue with your port, or with your toolchain.

> With toolchain OSELAS.2011.11.2 everything worked fine.
> We didn't change anything else.

Then this smells like a tool chain issue.  You might contact
Pengutronix support for help with their tool chain.

> So I suppose this might be a mainline problem.
> It seems like the mentioned variables don't get set correctly as before.

Well, no such problems are observed with mainline code and - for
example - ELDK 5.5 and 5.4-M3-rc1.  What makes you think it's a
mainline issue?  Can you prove such problems with mainline code, and
with a known to be working tool chain?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
1 1 was a race-horse, 2 2 was 1 2. When 1 1 1 1 race, 2 2 1 1 2.

  parent reply	other threads:[~2013-02-01 21:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  7:55 [U-Boot] U-Boot Bug with newer GCC Priebe, Sebastian
2013-02-01 11:31 ` Wolfgang Denk
2013-02-01 17:41   ` Jeroen Hofstee
2013-02-01 21:42     ` Wolfgang Denk
2013-02-02 11:25       ` Jeroen Hofstee
     [not found]   ` <E70AF999396FDF4EAE40E195B847096109F5D6FD@SRVEXCH-2K10.CADCON.INTERN>
2013-02-01 21:36     ` Wolfgang Denk [this message]
2013-02-02  8:37   ` Heiko Schocher
2013-02-02 10:18     ` Jeroen Hofstee
2013-02-02 11:32       ` Albert ARIBAUD
2013-02-02 14:05         ` Jeroen Hofstee
2013-02-02 15:05           ` Marek Vasut
2013-02-02 21:23             ` Wolfgang Denk
2013-02-02 21:22           ` Wolfgang Denk
2013-02-02 21:44             ` Jeroen Hofstee
2013-02-04  7:11               ` Priebe, Sebastian
2013-02-04  8:49                 ` Albert ARIBAUD
2013-02-04 11:28                   ` Priebe, Sebastian
2013-02-04 11:35                     ` Albert ARIBAUD
2013-02-04 14:23                       ` Priebe, Sebastian
2013-02-04 14:32                         ` Albert ARIBAUD
2013-02-04 15:32                           ` Priebe, Sebastian
2013-02-04 20:49                             ` Wolfgang Denk
2013-02-02 15:43       ` Jeroen Hofstee
2013-02-02 17:38         ` Heiko Schocher
2013-02-02 16:50           ` Marek Vasut
2013-02-02 19:12         ` Jeroen Hofstee

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=20130201213629.AD73B20055E@gemini.denx.de \
    --to=wd@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 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.