Date: Fri, 20 Apr 2012 13:21:20 -0700 From: Jason Evans <jasone@canonware.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: Michael Pounov <misho@aitbg.com>, current@FreeBSD.org Subject: Re: /usr/bin/as: out of memory allocating 4194304 bytes after a total of 524288000 bytes Message-ID: <FB2068D8-23AB-4FD6-B56D-B684631F98D7@canonware.com> In-Reply-To: <99ABB17E-C564-475E-92B0-7DF92EE4CFEC@freebsd.org> References: <20120420125718.GD1582@albert.catwhisker.org> <20120420165558.b51c8b66.misho@aitbg.com> <4F91BDE1.4080802@FreeBSD.org> <A7FB12C8-20FE-405A-88D7-4B872E9544F5@freebsd.org> <4F91C2BB.1000808@FreeBSD.org> <99ABB17E-C564-475E-92B0-7DF92EE4CFEC@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 20, 2012, at 1:14 PM, Jason Evans wrote: > On Apr 20, 2012, at 1:10 PM, Dimitry Andric wrote: >> On 2012-04-20 21:54, Jason Evans wrote: >>> On Apr 20, 2012, at 12:49 PM, Dimitry Andric wrote: >>>> I think the best solution would be for jemalloc to avoid using = obvious >>>> names like "chunksize" for its globals, because it is basically a >>>> library that could be linked to any sort of program out there. >>>>=20 >>>> For example, it could prefix all its internal-use only globals with >>>> "jemalloc_" or some other mangling scheme. Jason, any thoughts? >>>=20 >>> jemalloc has optional namespace mangling support built in for just = this reason. I'll turn it on, hopefully today. >>=20 >> Indeed, I had just found jemalloc/internal/private_namespace.h. :) = It >> does seem to list only functions, not variables, is that right? >=20 > Ah right, functions only. Well then, I don't have any bright ideas = for solving this problem in the short run. I take it back. There's spotty mangling coverage for variables. I'll = try to add full coverage. Jason=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FB2068D8-23AB-4FD6-B56D-B684631F98D7>