From: Dmytro Bablinyuk <dmytro.bablinyuk@rftechnology.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot and gcc 4.0
Date: Tue, 04 Oct 2005 17:03:56 +1000 [thread overview]
Message-ID: <dht9gi$cos$1@sea.gmane.org> (raw)
I have noticed today that u-boot uses some techniques that were
deprecated in 3.4.x and now removed in 4.0 (so I cannot just get source
and compile it under 4.0)
For example in u-boot/fs/jffs2/compr_rubin.c
temp = *(++((u32 *) in));
compr_rubin.c:89: error: invalid lvalue in increment
...
According to the gcc 4.0.0 changelog:
--8<--
The cast-as-lvalue, conditional-expression-as-lvalue and
compound-expression-as-lvalue extensions, which were deprecated in 3.3.4
and 3.4, have been removed.
--8<--
Is there are any plans to support 4.0 compiler or shall I downgrade my
compiler to 3.4.x version. I may try to fix such places but since I have
another task such as get our board running I am quite afraid to
introduce a new problems.
Thank you
Dimitry
next reply other threads:[~2005-10-04 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 7:03 Dmytro Bablinyuk [this message]
2005-10-04 8:17 ` [U-Boot-Users] u-boot and gcc 4.0 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='dht9gi$cos$1@sea.gmane.org' \
--to=dmytro.bablinyuk@rftechnology.com.au \
--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