On Wed, Jan 02, 2002 at 11:56:25PM -0800, Andrew Morton wrote:
> Oh well. Seems that disabling -fno-common and enabling
> --warn-common is the only way to autodetect bugs such as this.
You open another can of worms with variables in drivers that should be
static that aren't - you end up with no way to detect these without
So, you have a choice:
1. Enable -fno-common
- detect variables that should be marked static which aren't
- don't detect size differences
2. Disable -fno-common
- don't detect variables that should be marked static
- detect size differences as long as the variables aren't marked extern
As soon as someone has int foo in one file, and extern char foo in another,
you've lost no matter which option you take.
The header file approach is the most reliable (and imho correct) method to
solve this problem.
-- Russell King (email@example.com) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 07 2002 - 21:00:20 EST