> (I am thinking of more modular compilers, ones that behave differently than > ones we have today, but I won't get into that here).
Why not? This seems exactly fitting for a font discussion? If I were to distill the work down I would say its about finding powerful architectures for 2 things. 1) generative code / algorithms 2) containers powerful enough to contain and abstract the generated stuff. shawn > > -Mason Bially > > On Mon, Jul 9, 2012 at 11:23 PM, Shawn Morel <[email protected]> wrote: > Just watched a very interesting talk on memristors: > https://www.youtube.com/watch?v=bKGhvKyjgLY&feature=related > > I hadn't bothered going into very much detail so far - for some reason, I > thought memristors would end up being primarily used as memory elements that > supplant the traditional sram, dram, HDD hierarchy. That on its own is kind > of cool and would probably help shift us away from files and more towards > long-lived objects. > > The talk, however, describes ways that memristors can be organized to be an > arbitrary combination of switching, memory, logic or even analog emulations > of synaptic behaviour. The talk touches briefly on compiling from C down to > logic gates (Russell's material implication). Some key aspects is that, as > opposed to FPGAs the "reprogramming" can take place in a very short time and > they addressing capabilities of a HW associative memory are quite large. > > For example, it could take a few nanoseconds to create HW N-way associative > lookup - that's to say, I could on the fly configure a piece of HW to > actually represent object message dispatch! > > shawn > > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
