Date: Fri, 20 Apr 2012 14:11:00 -0700 From: Julian Elischer <julian@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: Michael Pounov <misho@aitbg.com>, Jason Evans <jasone@canonware.com>, current@freebsd.org Subject: Re: /usr/bin/as: out of memory allocating 4194304 bytes after a total of 524288000 bytes Message-ID: <4F91D0E4.7030004@freebsd.org> In-Reply-To: <4F91C8FE.4070807@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> <FB2068D8-23AB-4FD6-B56D-B684631F98D7@canonware.com> <4F91C8FE.4070807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/20/12 1:37 PM, Dimitry Andric wrote: > On 2012-04-20 22:21, Jason Evans wrote: >> 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. >>>>>> >>>>>> For example, it could prefix all its internal-use only globals >>>>>> with >>>>>> "jemalloc_" or some other mangling scheme. Jason, any thoughts? >>>>> >>>>> jemalloc has optional namespace mangling support built in for >>>>> just this reason. I'll turn it on, hopefully today. >>>> >>>> Indeed, I had just found jemalloc/internal/private_namespace.h. >>>> :) It >>>> does seem to list only functions, not variables, is that right? We do that with our driver.. variables and functions.. the symbols are all mangled in the .o file. >>> >>> 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. > > I'm now using the attached. It seems to work... > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F91D0E4.7030004>