5 May
2011
5 May
'11
7:12 a.m.
On Thu, May 05, 2011 at 11:56:42AM +0200, Peter Simons wrote:
Hi Matthew,
While I haven't investigated myself, from seeing haskell build processes in the past this is almost certainly not crypto-api's fault and is in fact your linker's fault. If you are not using it already, try switching to gold over ld, it may help.
well, memory consumption sky-rockets while compiling "Crypto.CPoly". That behavior is probably not related to the linker.
That's more than likely linked to the huge dispatch table related to cpoly. It would probably helps to build a vector with the data instead of this. -- Vincent