public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49688] [alpha]: Many execution test failures Date: Sat, 06 Aug 2011 07:21:00 -0000 [thread overview] Message-ID: <bug-49688-4-Nw3aaxXMPj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49688-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49688 --- Comment #22 from Uros Bizjak <ubizjak at gmail dot com> 2011-08-06 07:21:06 UTC --- (In reply to comment #21) > There are two remaining problems, an assert in "as", as reported in [2] > > FAIL: g++.dg/tree-prof/partition2.C compilation, -Os -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition2.C execution, -Os -fprofile-use This is PR 49972, reportedly fixed in binutils [1]. > FAIL: g++.dg/tree-prof/partition1.C compilation, -g -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -g -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -O0 -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O0 -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -O1 -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O1 -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -O2 -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O2 -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -O3 -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O3 -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -O3 -g -fprofile-use > (internal compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O3 -g -fprofile-use > FAIL: g++.dg/tree-prof/partition1.C compilation, -Os -fprofile-use (internal > compiler error) > UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -Os -fprofile-use This is now reported as PR 50001. [1] http://sourceware.org/ml/binutils/2011-08/msg00057.html
next prev parent reply other threads:[~2011-08-06 7:21 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-09 9:57 [Bug target/49688] New: " ubizjak at gmail dot com 2011-07-14 19:38 ` [Bug target/49688] " ubizjak at gmail dot com 2011-07-14 19:39 ` ubizjak at gmail dot com 2011-07-14 19:44 ` ubizjak at gmail dot com 2011-07-14 19:56 ` ubizjak at gmail dot com 2011-07-14 19:58 ` ubizjak at gmail dot com 2011-07-14 20:17 ` bernds at gcc dot gnu.org 2011-07-14 20:32 ` ubizjak at gmail dot com 2011-07-14 20:34 ` ubizjak at gmail dot com 2011-07-14 20:37 ` rth at gcc dot gnu.org 2011-07-14 20:41 ` bernds at gcc dot gnu.org 2011-07-14 21:13 ` ubizjak at gmail dot com 2011-07-14 21:22 ` bernds at gcc dot gnu.org 2011-07-14 21:28 ` ubizjak at gmail dot com 2011-07-14 21:34 ` rth at gcc dot gnu.org 2011-07-15 7:09 ` ubizjak at gmail dot com 2011-08-02 6:17 ` ubizjak at gmail dot com 2011-08-02 23:40 ` rth at gcc dot gnu.org 2011-08-05 17:33 ` rth at gcc dot gnu.org 2011-08-05 17:45 ` rth at gcc dot gnu.org 2011-08-05 19:04 ` rth at gcc dot gnu.org 2011-08-06 6:30 ` ubizjak at gmail dot com 2011-08-06 7:21 ` ubizjak at gmail dot com [this message] 2011-08-06 7:25 ` ubizjak at gmail dot com 2011-08-06 18:59 ` ubizjak at gmail 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-49688-4-Nw3aaxXMPj@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).