Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763500AbXJZPev (ORCPT ); Fri, 26 Oct 2007 11:34:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754394AbXJZPeo (ORCPT ); Fri, 26 Oct 2007 11:34:44 -0400 Received: from mx2.redhat.com ([66.187.237.31]:49760 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752946AbXJZPen (ORCPT ); Fri, 26 Oct 2007 11:34:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18210.2314.57767.962503@zebedee.pink> Date: Fri, 26 Oct 2007 16:34:34 +0100 From: Andrew Haley To: Linus Torvalds Cc: Bart Van Assche , linux-kernel@vger.kernel.org Subject: Re: Is gcc thread-unsafe? In-Reply-To: References: X-Mailer: VM 7.19 under Emacs 22.0.93.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 992 Lines: 23 Linus Torvalds writes: > So my basic worry about gcc is in fact none of the individual > technical problems themselves - those can be fixed. No, the problem > I've seen in gcc is that _some_ of the developers seem to be total > d*ckheads when it comes to "language definition", and seem to think > that it's more important to read the language spec like a lawyer > than it is to solve actual user problems. Well, yeah. I know what you mean. However, at this moment, some gcc developers are trying really hard not to be total d*ckheads about this issue, but get gcc fixed. Give us a chance. Andrew. -- Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK Registered in England and Wales No. 3798903 - 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/