Re: 1 GB limit on total object files size for linking?
Re: 1 GB limit on total object files size for linking?
- Subject: Re: 1 GB limit on total object files size for linking?
- From: "Helmut Brandt" <email@hidden>
- Date: Tue, 28 Aug 2007 07:46:16 -0700
Jason,
I have tried this with no debug, and with stabs and with Dwarf, and
Dwark +dSYM. Nothing works. In all cases I have object files over 1GB,
and it refuses to link.
So, my question remains: Where does the apparent 1 GB limitation come
from? GCC, Xcode, the OS, the amount of RAM I have, or ??
Helmut
On Mon, 27 Aug 2007 17:40:21 -0700, "Jason Molenda" <email@hidden>
said:
> Helmut,
>
> On Aug 27, 2007, at 5:26 PM, Helmut Brandt wrote:
>
> > Summary: Can't link 1.2GB collection of object files, compiled to
> > Intel
> > architecture.
>
> Is that 1.2GB with debug information or without?
>
> I'm assuming it's with debug information. And I'm assuming you're
> using stabs as your debug format. The linker had to process all of
> the stabs which led to slow link times and large linker memory usage
> -- and the problems you're seeing for certain large programs. This
> was one of the problems we addressed during the DWARF transition; the
> linker doesn't need to process the DWARF debug information. Can you
> try switching to DWARF + dSYM and see how that works for your project?
>
> Jason
--
Helmut Brandt
email@hidden
>
> I have a large program of roughly 1000 object files, which together
> total about 1.2 GB in size. The largest individual object file is about
> 7 MB, and they range down to as small as 3 KB. The files themselves are
> simple, but large, collections of floating point multiplies and
> additions. The Xcode project is just a "Command Line Utility standard
> tool", written in plain C. No frameworks. The only included libraries
> are stdio.h, stdlib.h, string.h, and math.h.
>
> The executable is a CGI script.
>
> I can successfully compile the files, but when I attempt to link them, I
> get the following message:
>
> /usr/bin/ld: can't vm_allocate() buffer for output file of size
> 1235753308 ((os/kern) no space available)
> collect2: ld returned 1 exit status
>
> My machine is a Mac Mini Intel Core Duo (not Intel Core 2 Duo) with 2GB
> of RAM and over 30 GB of available HD space. I am running OS X 10.4.10,
> with XCode tools version 2.4.1.
>
> I am compiling to Intel architecture only. By the way, I can
> successfully compile, link, and run a PowerPC version of this exact
> same code. The PPC produces an executable of about 700 MB (yes, the code
> grew from 700MB to 1.2GB going from PPC to Intel. For that reason, I am
> wondering if there is a 1GB limit imposed somewhere on the total
> executable size?
>
> Is this some sort of 32 bit limitation in the Mac OS, a GCC limitation,
> an Intel Core Duo limitation, or an Xcode limitation? Or, is it an "I
> don't know what I am doing limitation? (very possibly)
>
> Do I simply need more RAM? Unfortunately, my Mac Mini is maxed out at 2
> GB already. Or, would somehow a Core 2 Duo instead of my Core Duo help?
> Or do I need to wait for Leopard to link files of that size? (64 bit vs
> 32 bit)
>
> Or, is there just a magic terminal command or Xcode setting that I can
> execute to allow larger files
>
> Or, should I be doing some sort of dynamic linking to avoid an
> executable of that size? I am by no means an experienced programmer, so
> take it slow!
> --
> Helmut Brandt
> email@hidden
>
> --
> http://www.fastmail.fm - Does exactly what it says on the tin
>
--
Helmut Brandt
email@hidden
--
http://www.fastmail.fm - IMAP accessible web-mail
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden