public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "werner at beroux dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67571] Error: open CFI at the end of file; missing .cfi_endproc directive Date: Mon, 14 Sep 2015 11:02:00 -0000 [thread overview] Message-ID: <bug-67571-4-WsX3W8d1GS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67571-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67571 --- Comment #6 from werner at beroux dot com --- Humm no sorry I'm building from the same git tag (which is of Jan 24). So it looks like something caused GCC to use more memory than before. I did notice a GCC5 compilation fix, probably unrelated, just in case it here: https://github.com/ariya/phantomjs/commit/fe2c6bb5fdf776b718422a104e6babe67dbf2629
next prev parent reply other threads:[~2015-09-14 11:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-14 10:05 [Bug c++/67571] New: " werner at beroux dot com 2015-09-14 10:13 ` [Bug c++/67571] " mpolacek at gcc dot gnu.org 2015-09-14 10:43 ` werner at beroux dot com 2015-09-14 10:48 ` mpolacek at gcc dot gnu.org 2015-09-14 10:56 ` werner at beroux dot com 2015-09-14 11:02 ` werner at beroux dot com [this message] 2015-09-14 11:20 ` trippels at gcc dot gnu.org 2015-09-15 8:07 ` werner at beroux dot com 2015-09-16 15:21 ` werner at beroux dot com 2015-09-16 15:26 ` trippels at gcc dot gnu.org 2015-09-16 18:53 ` werner at beroux 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-67571-4-WsX3W8d1GS@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: linkBe 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).