From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Bug with newer GCC
Date: Fri, 01 Feb 2013 18:41:28 +0100 [thread overview]
Message-ID: <510BFE48.3060206@myspectrum.nl> (raw)
In-Reply-To: <20130201113111.DC53920055E@gemini.denx.de>
Hi Wolfgang,
On 02/01/2013 12:31 PM, Wolfgang Denk wrote:
>> We recently tried a new toolchain with GCC 4.7.2.
>> If compiled with the new toolchain the feature CONFIG_AUTO_COMPLETE isn't working.
> We have been using GCC 4.7.2 for several months now, on many systems.
> No such problems have been reported before, so I speculate if this is
> really a problem with mainline code?
The twister board has the same problem, tested
4e5eb45898b6f05fef3a4690399726c03bc1f398 with twister_config /
eldk 5.3 on a twister board (and it traps). So it does occur in mainline,
but it must be a combination of board config and code or something,
since also Albert did not know / didn't have this problem.
Regards,
Jeroen
next prev parent reply other threads:[~2013-02-01 17:41 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 [this message]
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
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=510BFE48.3060206@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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.