public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jpyeron at pdinc dot us" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64414] cc1plus: internal compiler error: Segmentation fault Date: Fri, 26 Dec 2014 19:39:00 -0000 [thread overview] Message-ID: <bug-64414-4-m5vQBetUpp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64414 --- Comment #1 from Jason Pyeron <jpyeron at pdinc dot us> --- In an attempt to be lazy, I added a .h file to refer to a .h file in the parent directory. 2154b9ff583610a5ab97821ed6b45646df2f4e2b:src/Main/Unix/System.h: #include "../System.h" removing that file eliminates the crash.
next prev parent reply other threads:[~2014-12-26 19:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-26 19:29 [Bug c++/64414] New: " jpyeron at pdinc dot us 2014-12-26 19:39 ` jpyeron at pdinc dot us [this message] 2014-12-27 15:22 ` [Bug c++/64414] " hjl.tools at gmail dot com 2014-12-27 16:59 ` jpyeron at pdinc dot us 2014-12-28 13:54 ` jpyeron at pdinc dot us 2015-01-12 14:19 ` jakub at gcc dot gnu.org
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-64414-4-m5vQBetUpp@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).