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 target/58491] New: FAIL: ext/random/normal_mv_distribution/cons/default.cc (test for excess errors) Date: Sat, 21 Sep 2013 14:20:00 -0000 [thread overview] Message-ID: <bug-58491-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58491 Bug ID: 58491 Summary: FAIL: ext/random/normal_mv_distribution/cons/default.cc (test for excess errors) Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org Host: hppa64-hp-hpux* Target: hppa64-hp-hpux* Build: hppa64-hp-hpux* Created attachment 30877 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30877&action=edit Preprocessed source spawn /test/gnu/gcc/objdir/./gcc/xg++ -shared-libgcc -B/test/gnu/gcc/objdir/./gcc -nostdinc++ -L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/libstdc++-v3/src -L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/libstdc++-v3/src/.libs -L/test/gnu/gcc/objd ir/hppa64-hp-hpux11.11/libstdc++-v3/libsupc++/.libs -B/opt/gnu64/gcc/gcc-4.9/hpp a64-hp-hpux11.11/bin/ -B/opt/gnu64/gcc/gcc-4.9/hppa64-hp-hpux11.11/lib/ -isystem /opt/gnu64/gcc/gcc-4.9/hppa64-hp-hpux11.11/include -isystem /opt/gnu64/gcc/gcc- 4.9/hppa64-hp-hpux11.11/sys-include -B/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs -D_GLIBCXX_ASSERT -fmessage-length=0 -ffunction-sections -fdata-sections -g -O2 -g -O2 -DLOCALEDIR="." -nostdinc++ -I/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/libstdc++-v3/include/hppa64-hp-hpux11.11 -I/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/libstdc++-v3/include -I/test/gnu/gcc/gcc/libstdc++-v3/libsupc++ -I/test/gnu/gcc/gcc/libstdc++-v3/include/backward -I/test/gnu/gcc/gcc/libstdc++-v3/testsuite/util /test/gnu/gcc/gcc/libstdc++-v3/testsuite/ext/random/normal_mv_distribution/cons/default.cc -std=c++0x ./libtestc++.a -lm -o ./default.exe /test/gnu/gcc/gcc/libstdc++-v3/testsuite/ext/random/normal_mv_distribution/cons/default.cc: In constructor '__gnu_cxx::normal_mv_distribution<_Dimen, _RealType>::param_type::param_type() [with long unsigned int _Dimen = 2ul; _RealType = double]': /test/gnu/gcc/gcc/libstdc++-v3/testsuite/ext/random/normal_mv_distribution/cons/default.cc:49:1: internal compiler error: in build_polynomial_chrec, at tree-chrec.h:148 } ^ libbacktrace could not find executable to open /test/gnu/gcc/objdir/./gcc/cc1plus -fpreprocessed default.ii -quiet -dumpbase d efault.cc -auxbase default -g -g -O2 -O2 -std=c++11 -version -fmessage-length=0 -ffunction-sections -fdata-sections -o default.s
next reply other threads:[~2013-09-21 14:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-21 14:20 danglin at gcc dot gnu.org [this message] 2013-09-21 14:35 ` [Bug tree-optimization/58491] " danglin at gcc dot gnu.org 2013-09-21 14:38 ` danglin at gcc dot gnu.org 2013-09-21 17:02 ` paolo.carlini at oracle dot com 2013-09-23 9:32 ` rguenth 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-58491-4@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).