public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "miyuki at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/66237] [6 regression] FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE (internal compiler error)
Date: Mon, 06 Jul 2015 22:03:00 -0000 [thread overview]
Message-ID: <bug-66237-4-rmQffXVdEU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66237-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66237
Mikhail Maltsev <miyuki at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Mikhail Maltsev <miyuki at gcc dot gnu.org> ---
Though I could not fully test this fix myself (I don't have an aarch64 box), I
suppose that it's safe to rely on test results published on the mailing list:
https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg02567.html - fail
https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg02714.html - pass
Thus, fixed for GCC 6.
prev parent reply other threads:[~2015-07-06 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 9:26 [Bug rtl-optimization/66237] New: [6.0 " schwab@linux-m68k.org
2015-05-21 10:41 ` [Bug rtl-optimization/66237] [6 " rguenth at gcc dot gnu.org
2015-05-21 14:04 ` miyuki at gcc dot gnu.org
2015-05-21 14:10 ` schwab@linux-m68k.org
2015-05-21 14:19 ` schwab@linux-m68k.org
2015-05-21 21:27 ` schwab@linux-m68k.org
2015-05-22 22:58 ` miyuki at gcc dot gnu.org
2015-07-06 22:03 ` miyuki at gcc dot gnu.org [this message]
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-66237-4-rmQffXVdEU@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).