On Wed, 2012-02-08 at 11:16 -0500, Jean Delvare wrote: > On Wed, 8 Feb 2012 08:06:58 -0800, Guenter Roeck wrote: > > Would it be worthwhile trying to track this down further ? 4.4.6 is the latest gcc > > version from the 4.4 series, so the problem might bite us again. > > I'd suggest that Patrick reports the problem to the maintainer of the > gcc package in his distribution. Who knows what local patches they may > have applied? If that doesn't help then the next step would be to > reproduce the problem with upstream gcc 4.4.6. If the bug is still > there, try upstream 4.4.5, etc. If this is a regression in the gcc 4.4 > branch, and you can give the exact version it happened in, upstream > developers will certainly listen. > Agreed, that might be the best approach. Patrick, where do you get the 4.4.6 compiler from ? Is it from debian or from a different distribution ? Do you know the exact package version (the latest debian version is 4.4.6-14, for example) ? Thanks, Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
