From: Jean Delvare <khali@linux-fr.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Greg KH <gregkh@suse.de>, Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, i2c@lm-sensors.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: Various problems on Axis 700 Lite VIA C7
Date: Fri, 5 Oct 2007 23:13:06 +0200 [thread overview]
Message-ID: <20071005231306.447e91f8@hyperion.delvare> (raw)
In-Reply-To: <Pine.LNX.4.60.0710052215510.10392@poirot.grange>
Hi Guennadi,
On Fri, 5 Oct 2007 22:22:08 +0200 (CEST), Guennadi Liakhovetski wrote:
> 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
prev parent reply other threads:[~2007-10-05 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 23:19 [IRQ map] VIA C7 CN700 2.6.23-rc9-git USB IRQs disabled Guennadi Liakhovetski
2007-10-05 14:25 ` [linux-usb-devel] " Alan Stern
2007-10-05 14:50 ` Guennadi Liakhovetski
2007-10-05 20:22 ` Various problems on Axis 700 Lite VIA C7 Guennadi Liakhovetski
2007-10-05 20:47 ` Michael Tokarev
2007-10-05 21:30 ` Guennadi Liakhovetski
2007-10-06 15:10 ` [i2c] " Guennadi Liakhovetski
2007-10-05 21:13 ` Jean Delvare [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071005231306.447e91f8@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@suse.de \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox