Hi Guennadi,

On Fri, 5 Oct 2007 22:22:08 +0200 (CEST), Guennadi Liakhovetski wrote:
quoted text
> Ok, after a day of biseting, it turns out to be a compiler problem. The 
> gcc-3.3.5 produces at least these two problems (Oops on i2c-viapro probe 
> and disabled IRQs in USB), whereas 4.1.2 has no problem so far. Up to now 
> 3.3.5 had no problem compiling 2.6.20+ kernels here, for example, for P-II 
> SMP. Does it at all look realistic that such "random" run-time problems 
> are caused by a miscompilation?...

Miscompilation can do about anything. There have been a number of other
reports about compiler issues lately. Ingo Molnar here:
http://kerneltrap.org/Linux/Compiler_Optimization_Bugs_and_World_Domination
Me here:
http://marc.info/?l=linux-kernel&m=119127234804440&w=2

The trend I am seeing is that we are optimizing for, and testing with,
recent compilers (gcc 4.1 and later) and that older compilers tend to
break, even though compilers as old as gcc 3.2 are still supposed to be
supported. Not good.

-- 
Jean Delvare
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/