public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64837] lto plugin doesn't call ld_plugin_release_input_file
Date: Wed, 11 Feb 2015 12:49:00 -0000 [thread overview]
Message-ID: <bug-64837-4-YvnsuZ7pvu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64837-4@http.gcc.gnu.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.
next prev parent reply other threads:[~2015-02-11 12:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:24 [Bug lto/64837] New: lto plugun " hjl.tools at gmail dot com
2015-01-28 14:30 ` [Bug lto/64837] " trippels at gcc dot gnu.org
2015-01-28 14:33 ` hjl.tools at gmail dot com
2015-01-28 18:46 ` [Bug lto/64837] lto plugin " hjl.tools at gmail dot com
2015-01-28 19:40 ` hjl at gcc dot gnu.org
2015-01-28 19:41 ` hjl.tools at gmail dot com
2015-02-06 13:29 ` burnus at gcc dot gnu.org
2015-02-06 13:56 ` hjl at gcc dot gnu.org
2015-02-06 13:56 ` hjl.tools at gmail dot com
2015-02-11 12:38 ` hjl.tools at gmail dot com
2015-02-11 12:39 ` hjl.tools at gmail dot com
2015-02-11 12:44 ` hjl.tools at gmail dot com
2015-02-11 12:49 ` trippels at gcc dot gnu.org [this message]
2015-02-11 15:34 ` trippels at gcc dot gnu.org
2015-02-11 15:40 ` hjl.tools at gmail dot com
2015-02-11 15:43 ` trippels at gcc dot gnu.org
2015-02-11 15:47 ` hjl.tools at gmail dot com
2015-02-11 15:52 ` trippels at gcc dot gnu.org
2015-02-12 9:04 ` marxin at gcc dot gnu.org
2015-02-12 12:23 ` hjl.tools at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64837-4-YvnsuZ7pvu@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).