On Mon, Jul 29, 2013 at 3:31 AM, Matt Rice <[email protected]> wrote:
> On Sat, Jul 27, 2013 at 11:42 AM, Jonathan S. Shapiro <[email protected]>wrote: > >> On Sat, Jul 27, 2013 at 11:11 AM, Ian P. Cooke <[email protected]> wrote: >> >> >>> you need to access specific addresses (memory-mapped devices), >>> >> >> Potentially for kernel or driver code. >> > > I'd personally rather this not be the case and do it elsehow > with something in the vein of termite and the devil idl compiler > even if the output of this is linked in to the executable with other bitc > object files when needed... > Unfortunately that isn't practical for some things. Kernel code is inherently unsafe. What needs to happen is for raw addresses to be relegated to an unsafe language subset.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
