On 01/22/2013 07:41 AM, Mark Brown wrote:
(..)
> This sort of fix is not a good idea, you're just shutting the
> warning up without any sort of analysis explaining why it's
> generated in error. If it's generating a spurious error that's a
> compiler bug.
In the regmap_debugfs_get_dump_start() function control flow, I think
the compiler cannot know for sure that the list_for_each_entry()
iterates at least once.:
regmap_debugfs_get_dump_start()
{
unsigned int ret;
<snip some code, which does not touch ret>
list_for_each_entry() {
<snip some code>
ret = <value>;
}
return ret;
}
Do you think there is a way to "mark" the list_for_each_entry() as
iterating at least once? an __attribute__ maybe?
Best regards,
V.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
