public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/65319] FAIL: g++.dg/other/dump-ada-spec-3.C -std=gnu++98 (internal compiler error) Date: Thu, 05 Mar 2015 00:38:00 -0000 [thread overview] Message-ID: <bug-65319-4-ROjvpWk1F4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65319-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65319 --- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> --- spawn /home/dave/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++ -B/home/dave/gnu/gc c/objdir/gcc/testsuite/g++/../../ /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/ot her/dump-ada-spec-3.C -fno-diagnostics-show-caret -fdiagnostics-color=never -nos tdinc++ -I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/hppa-lin ux-gnu -I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include -I/home/d ave/gnu/gcc/gcc/libstdc++-v3/libsupc++ -I/home/dave/gnu/gcc/gcc/libstdc++-v3/inc lude/backward -I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -std=gnu++98 -fdump-ada-spec -S -o dump-ada-spec-3.s /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/other/dump-ada-spec-3.C:25:1: intern al compiler error: Segmentation fault 0x6baee3 crash_signal ../../gcc/gcc/toplev.c:383Please submit a full bug report, Failure is not fully consistent and I was unable to get test to ICE running in under gdb on linux. Test also ICE's on hpux.
next prev parent reply other threads:[~2015-03-05 0:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-05 0:36 [Bug ada/65319] New: " danglin at gcc dot gnu.org 2015-03-05 0:38 ` danglin at gcc dot gnu.org [this message] 2015-03-05 12:19 ` [Bug ada/65319] " ebotcazou at gcc dot gnu.org 2015-03-05 13:56 ` ebotcazou at gcc dot gnu.org 2015-03-05 13:56 ` ebotcazou 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-65319-4-ROjvpWk1F4@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).