From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 17 Jul 2011 11:08:27 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-ID: <20110717110827.1ab754d1@lahti.ethans.dre.am> In-Reply-To: <201107162256.53336.dexen.devries@gmail.com> References: <20110715151535.GA2405@polynum.com> <20110716180627.GA29488@polynum.com> <201107162256.53336.dexen.devries@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [9fans] NUMA Topicbox-Message-UUID: 03219138-ead7-11e9-9d60-3106f5b1d025 On Sat, 16 Jul 2011 22:56:53 +0200 dexen deVries wrote: > On Saturday 16 July 2011 21:54:33 erik quanstrom wrote: > > it's interesting you bring this up. risc has largely been removed > > from architectures. if you tie the instruction set and machine model > > to the actual hardware, then you need to write new compilers and > > recompile everything every few years. instead, the risc is hidden > > and the instruction set stays the same. this allows for a lot of > > under-the-hood innovation in isolation from the architecture. > > > interesting angle. till now i believed it's easier to innovate in software > (even compilers) than in silicon. where did we go wrong that silicon became > the easier way? would it be fair to blame GCC and other heavyweight champions? Gcc has mutual incompatibilities between different versions of itself, caused by its attempts to correctly interpret the heavyweight C standards we have today, but I wouldn't say gcc is the big problem. Some of the most essential libraries in a Linux system are real bugbears to compile, particularly for a new arch. I'd say it's just part of the ossification of software today. It's become extremely rigid and brittle, perhaps even more so in open source than commercial contexts.