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 c++/67571] Error: open CFI at the end of file; missing .cfi_endproc directive
Date: Wed, 16 Sep 2015 15:26:00 -0000	[thread overview]
Message-ID: <bug-67571-4-8R5djxFfXx@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 #10 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to werner from comment #9)
> (In reply to Markus Trippelsdorf from comment #7)
> > Can you please attach the preprocessed JSBindingsAllInOne.ii file (by
> > adding -save-temps to the compiler invocation)?
> 
> I added that flag (at least I think it worked) but I find any file of that
> name below /tmp/phantomjs (my build directory). Do you know where it's
> supposed to be generated at?

In the directory from which you've invoked gcc.

So in your case:
cd /tmp/phantomjs/src/qt/qtwebkit/Source/WebCore
g++ --save-temps -c  -Wall -Wextra -Wreturn-type ... (from comment 0)

You'll find JSBindingsAllInOne.ii in
/tmp/phantomjs/src/qt/qtwebkit/Source/WebCore


  parent reply	other threads:[~2015-09-16 15:26 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
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 [this message]
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-8R5djxFfXx@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).