search for: gold64

On Nov 14, 2013, at 8:19 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > But gold has at most 2 objects loaded at any time. Are you sure about that? I haven't looked into it but while building Chromium with LTO, I get: ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any clang: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn 10000 Looking in /proc, it has 10013 open file descri...

...; On Nov 14, 2013, at 8:19 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> But gold has at most 2 objects loaded at any time. > > Are you sure about that? I haven't looked into it but while building Chromium with LTO, I get: > > ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any > clang: error: linker command failed with exit code 1 (use -v to see invocation) > ninja: build stopped: subcommand failed. > [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn > 10000 > > Looking in /proc,...

...AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> >>> But gold has at most 2 objects loaded at any time. >> >> Are you sure about that? I haven't looked into it but while building Chromium with LTO, I get: >> >> ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any >> clang: error: linker command failed with exit code 1 (use -v to see invocation) >> ninja: build stopped: subcommand failed. >> [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn >> 10000 >> &g...

...<rafael.espindola at gmail.com> wrote: >>> >>>> But gold has at most 2 objects loaded at any time. >>> >>> Are you sure about that? I haven't looked into it but while building Chromium with LTO, I get: >>> >>> ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any >>> clang: error: linker command failed with exit code 1 (use -v to see invocation) >>> ninja: build stopped: subcommand failed. >>> [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn >>> 10...

> Letting the module own MDNodes may not be a win for gold since it is going > to create multiple copies of MDNodes that could be shared with Context > owning MDNodes. > > For example, with debug info type uniquing, the type nodes can be shared > across modules, but with module owning MDNodes, each module will create its > own copy of the type nodes. The advantage is that the

On Wed, Nov 13, 2013 at 7:58 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > > It sounds like the linker could call lto_module_dispose() right after > > lto_codegen_add_module() to help reduce the memory footprint. That > would be > > a simple linker change. A slightly larger linker change would be to > > immediately call lto_codegen_add_module()