From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Tue May 12 16:09:36 EDT 2020
Message-ID: <2836601DDD0CD6197CC052B317693241@felloff.net>
Date: Tue, 12 May 2020 22:09:20 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] 5l breakage on zynq
In-Reply-To: <4B65C95D9EB2FB2BF18754CBF0C978B7@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: social asynchronous map/reduce SOAP replication proxy-aware configuration solution 

pushed a fix by removing all the hunk pointer fiddling from
the linker and put a explaination of the problem in the
commit message.

ori's patch is correct. but i think it is better just to
stop making all these internal hidden assumptions and just
use malloc().

overall, we might even start just phasing out the hunk stuff
and just use malloc()/relloc() calls, but link with a fast
non-freeing implementation from cc/.

--
cinap