Re: Is Safe Haskell intended to allow segfaults?

* Mikhail Glushenkov: > Hi, > > On 9 August 2016 at 01:32, David Terei wrote: >> I imagine in Java, that I can construct an invalid pointer in foreign >> code, and then cause segfaults without the Java code having any >> issues. Just guessing at this, so very interested to know how it's >> preven

Re: Do we have free bits in the info pointer itself?

* Ryan Newton: > Our heap object header is one word -- an info table pointer > . > > Well, a 64 bit info table pointer leaves *at least* 16 high bits inside the > object header for other purposes, right? x86_64 has signed p

Re: New primitive types?

* Michal Terepeta: > On Tue, Aug 1, 2017 at 8:08 PM Carter Schonwald > wrote: >> One issue with packed fields is that on many architectures you can't > quite do subword reads or >> writes. So it might not always be a win. > > Could you give any examples? Historic DEC Alpha, now long obsolete.

Re: New primitive types?

* Carter Schonwald: > Which architectures are which? > > I assume you mean the dec alpha allowed atomic operations on bytes... but > your phrasing is a teeny bit unclear Early DEC Alpha had only word access. ___ ghc-devs mailing list ghc-devs@haskell.or

Re: Why do we put GMP allocations on GHC heaps?

* Edward Z. Yang: > Actually, this is precisely the problem. When is a GMP integer freed? > It can have pointers to it from objects on the heap, so this free should > only occur when the integer is dead, with no references from the heap. > How can that be arranged? Well, the garbage collector is

Re: Why do we put GMP allocations on GHC heaps?

* Simon Marlow: > We did originally look at targetting the mpn API, but decided against > it for the reasons alluded to above - the mpz layer has quite a lot of > stuff in it that you would need to replicate. For instance, when you > start doing an operation some calculation has to be done to fig

[PATCH] sync-all: Skip END actions on exceptions

to get the new repository. == Checking for obsolete Git repo URL $ The patch corrects the error message. I've removed the --testsuite flag from the wiki page as well. >From 1877358f8bd3fe47cc2035902d9c51351c79b443 Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Thu,

C-- specfication

I'm looking for a specification of C--. I can't find it on the cminuscminus.org web site, and it's also not included in the release tarball. Does anybody know where to get it? ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman

Re: C-- specfication

* Yuras Shumovich: > Are you interested in ghc's cmm? It is different from the original C--. > (And it differs between ghc versions.) Actually, I'm interested in some form of Mini-C (in the spirit of Mini-ML or Featherweight Java) for some experiment, and I assumed that people here would know whe