From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lib/crc16: use non-C99 loop style
Date: Wed, 13 Feb 2019 19:31:33 -0500 [thread overview]
Message-ID: <20190214003133.GC21737@bill-the-cat> (raw)
In-Reply-To: <20190213215728.21603-1-thomas.petazzoni@bootlin.com>
On Wed, Feb 13, 2019 at 10:57:28PM +0100, Thomas Petazzoni wrote:
> Commit 51c2345bd24837f9f67f16268da6dc71573f1325 ("Roll CRC16-CCITT
> into the hash infrastructure") has modified the crc16 code by adding a
> C99-style loop where the loop iterator is declared inside the for()
> statement. This breaks the build with old compiler such as gcc 4.7,
> that do not default to C99:
>
> ./tools/../lib/crc16.c: In function 'crc16_ccitt':
> ./tools/../lib/crc16.c:70:2: error: 'for' loop initial declarations are only allowed in C99 mode
> ./tools/../lib/crc16.c:70:2: note: use option -std=c99 or -std=gnu99 to compile your code
>
> Switching to the regular coding style used in the rest of U-Boot
> allows to fix this build issue.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
So first, as Philipp notes we require gcc-6 or later for U-Boot itself.
But you're hitting this on the host and I assume something uncommon but
not unsupported yet where it's still on gcc-4.7. So I'm inclined to
allow the patch and just note that we're likely to have other breakage
in the future. Also, can you please v2 and reword with a Fixes tag
instead? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190213/a9344742/attachment.sig>
next prev parent reply other threads:[~2019-02-14 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 21:57 [U-Boot] [PATCH] lib/crc16: use non-C99 loop style Thomas Petazzoni
2019-02-13 22:50 ` Philipp Tomsich
2019-02-14 0:31 ` Tom Rini [this message]
2019-02-14 0:57 ` Philipp Tomsich
2019-02-14 7:56 ` Thomas Petazzoni
2019-02-14 11:35 ` Philipp Tomsich
2019-02-14 12:22 ` Tom Rini
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=20190214003133.GC21737@bill-the-cat \
--to=trini@konsulko.com \
--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