From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-kernel@vger.kernel.org, malitzke@metronets.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Bug 8501] udivdi3 absence with gcc-4.3.0 on kernels 2.6.20.11 & 2.6.22.-rc1
Date: Sat, 19 May 2007 01:05:49 +0200 [thread overview]
Message-ID: <20070518230549.GB6291@stusta.de> (raw)
In-Reply-To: <20070518152935.b5a4b3bf.akpm@linux-foundation.org>
On Fri, May 18, 2007 at 03:29:35PM -0700, Andrew Morton wrote:
>...
> I expect that this optimisation will remain in gcc-4.3 and we'll end up
> having major kernel releases which don't build on i386 with major gcc
> releases, which isn't altogether desirable. I suspect we'll need to fix this
> fairly urgently, and to backport the fix into a number of kernel releases.
>...
Building old kernels with the latest gcc has never worked [1].
First of all, gcc 4.3 is still one year away from being released, so
there's zero urgency.
And considering that compile errors are the trivial things, and the real
problems are new runtime errors caused by incorrect kernel code combined
with gcc optimization [2] I'd even consider backporting only the compile
fixes before the real issues have been shaken out a bad idea.
cu
Adrian
[1] the backported gcc 4 support in kernel 2.4 is an exception
[2] look e.g. at commit 8690ba446defe2e2b81803756c099d2943dfd5fd
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-05-18 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705181941.l4IJfOtf018049@fire-2.osdl.org>
2007-05-18 22:29 ` [Bug 8501] udivdi3 absence with gcc-4.3.0 on kernels 2.6.20.11 & 2.6.22.-rc1 Andrew Morton
2007-05-18 23:05 ` Adrian Bunk [this message]
2007-05-18 23:12 ` Thomas Gleixner
2007-05-18 23:15 ` Linus Torvalds
2007-05-18 23:39 ` Segher Boessenkool
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=20070518230549.GB6291@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malitzke@metronets.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.