linux-kernel - Re: Is gcc thread-unsafe?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18210.2314.57767.962503@zebedee.pink>
Date:	Fri, 26 Oct 2007 16:34:34 +0100
From:	Andrew Haley <aph@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Bart Van Assche <bart.vanassche@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Is gcc thread-unsafe?

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/