This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/64837] lto plugin doesn't call ld_plugin_release_input_file
- From: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 11 Feb 2015 12:48:57 +0000
- Subject: [Bug lto/64837] lto plugin doesn't call ld_plugin_release_input_file
- Auto-submitted: auto-generated
- References: <bug-64837-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64837
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #13 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #11)
> (In reply to Markus Trippelsdorf from comment #1)
> > > It may also leak file descriptor when gold is used.
> >
> > It certainly does. I ran into this issue when building Chromium with LTO.
> > (I just increased ulimit -n as a workaround)
>
> Can you try the patch
>
> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34725
Unfortunately no. It was possible to build Chromium with LTO
on my 8GB machine two years ago, but not anymore.
Maybe Martin can give it a try? CCing him.