News for hackers. Stuff that matters.
Re:Hidden Costs of Memory Allocation by adwn on Wednesday December 10, 2014 @11:58AM (#8730161)
The Mill [1] does/will do that: When memory is allocated, it is served directly be the cache, which implicitly zeroes the respective cache line (without involving the main memory).

A similar mechanism zeroes a stackframe upon a function call (and function return, I think), which eliminates most attacks that exploit buffer-overflows.

[1] http://millcomputing.com/docs/memory/

Re:Hidden Costs of Memory Allocation by oso2k on Wednesday December 10, 2014 @03:40PM (#8731546)
So a Mill CPU can never do shared-memory process parallelization? Two or more processes accessing the same memory could be a hazard. Seems like it would suffer the same issue IA-64 has with parallelism. However, the conveyor belt analogy simplifies register spilling & related issues.
Re:Hidden Costs of Memory Allocation by adwn on Thursday December 11, 2014 @01:15AM (#8733453)
> So a Mill CPU can never do shared-memory process parallelization?

Why not? The caches will still be coherent.

Re:Hidden Costs of Memory Allocation by crest on Wednesday December 10, 2014 @09:56PM (#8732946)
Only if you are crazy enough to share stacks in which case you deserve what you get.