Having looked at the same code to fix (what I presume are) the same "may
be used uninitialized" warnings, I am curious how you managed to trigger
these warnings? I have to wonder if you're using an older version of
gcc or a different set of optimizations.
--Z
On Tue, 2009-06-30 at 23:13 +0200, ntfreak at BerliOS wrote:
> Author: ntfreak
> Date: 2009-06-30 23:13:53 +0200 (Tue, 30 Jun 2009)
> New Revision: 2434
>
> Modified:
> trunk/src/flash/at91sam3.c
> Log:
> - remove cygwin build warnings in at91sam3.c
>
> Modified: trunk/src/flash/at91sam3.c
> ===================================================================
> --- trunk/src/flash/at91sam3.c 2009-06-30 20:44:21 UTC (rev 2433)
> +++ trunk/src/flash/at91sam3.c 2009-06-30 21:13:53 UTC (rev 2434)
> @@ -1308,9 +1308,9 @@
> static void
> sam3_explain_mckr(struct sam3_chip *pChip)
> {
> - uint32_t css, pres,fin;
> - int pdiv;
> - const char *cp;
> + uint32_t css, pres, fin = 0;
> + int pdiv = 0;
> + const char *cp = NULL;
>
> css = sam3_reg_fieldname(pChip, "CSS", pChip->cfg.PMC_MCKR, 0, 2);
> switch (css & 3) {
>
> _______________________________________________
> Openocd-svn mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/openocd-svn
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
