From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Martin Orr <martin@martinorr.name>,
Stefano Rivoir <s.rivoir@gts.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Thu, 12 Jul 2007 00:43:22 +0200 [thread overview]
Message-ID: <20070711224322.GC25510@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707111534340.20061@woody.linux-foundation.org>
On Wed, Jul 11, 2007 at 03:37:41PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 12 Jul 2007, Andi Kleen wrote:
> >
> > I just checked with today's gcc 4.2 (070711) freshly compiled and from a quick inspection
> > the code looks correct again. So perhaps it has been already fixed?
>
> Did you see the breakage with the original compiler? It might be some
No, i don't have a debian compiler and i normally use gcc 4.1 on my
workstation.
BTW I just heard that at least one package in suse STABLE (using a slightly
older gcc 4.2 snapshot) apprently with inline assembly got miscompiled too
> config setup or something.
>
> But yeah, if Debian/sid is just using random compiler snapshots of the
> day, I htink we can just bury this as "pointless".
>
> Who the heck takes a compiler snapshot and runs with it? At least when
> your kernel breaks, it seldom breaks subtly (but I would expect that most
> distros would not pick random nightly kernel builds). When your compiler
> breaks, you have random problems in totally unexpected places, the last
> thing you want to have is a random nightly snapshot in a distro - even a
> development one.
I guess it's because gcc 4.2 is technically supposed to be a -stable tree.
Also recompiling whole distros tends to find a lot of compiler bugs so
I guess it's useful QA for them.
-Andi
next prev parent reply other threads:[~2007-07-11 22:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 23:52 Linux 2.6.22 released Linus Torvalds
2007-07-09 0:19 ` Jesper Juhl
2007-07-09 1:08 ` Phil Oester
2007-07-09 6:06 ` Jan De Luyck
2007-07-09 5:00 ` Willy Tarreau
2007-07-09 10:14 ` Alan Cox
2007-07-10 18:41 ` Chuck Ebbert
2007-07-09 10:30 ` Jan Engelhardt
2007-07-09 11:45 ` Jan Engelhardt
2007-07-09 14:25 ` Michal Piotrowski
2007-07-10 7:17 ` Stefano Rivoir
2007-07-10 8:52 ` Andrew Morton
2007-07-10 15:39 ` Linus Torvalds
2007-07-10 15:59 ` Stefan Richter
2007-07-11 6:38 ` Stefano Rivoir
2007-07-11 7:05 ` Linus Torvalds
2007-07-11 10:55 ` Stephen Frost
2007-07-11 14:28 ` Stefano Rivoir
2007-07-11 12:35 ` Martin Orr
2007-07-11 14:27 ` Stefano Rivoir
2007-07-11 13:10 ` Andi Kleen
2007-07-11 17:51 ` Martin Orr
2007-07-11 18:01 ` Linus Torvalds
2007-07-11 21:00 ` Martin Orr
2007-07-11 21:29 ` Linus Torvalds
2007-07-11 22:16 ` Andi Kleen
2007-07-11 22:33 ` Serge Belyshev
2007-07-11 22:37 ` Linus Torvalds
2007-07-11 22:43 ` Andi Kleen [this message]
2007-07-11 23:56 ` Stephen Frost
2007-07-14 15:48 ` Martin Orr
2007-07-11 16:25 ` Theodore Tso
2007-07-10 19:39 ` Valdis.Kletnieks
2007-07-10 22:26 ` Adrian Bunk
2007-07-10 23:12 ` Stefan Richter
2007-07-11 0:00 ` Adrian Bunk
2007-07-11 10:57 ` Stefan Richter
2007-07-11 0:32 ` Valdis.Kletnieks
2007-07-11 0:01 ` david
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=20070711224322.GC25510@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@martinorr.name \
--cc=s.rivoir@gts.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox