public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/58553] New fail in PASS->FAIL: gcc.c-torture/execute/memcpy-2.c execution on arm and aarch64 Date: Fri, 27 Sep 2013 19:37:00 -0000 [thread overview] Message-ID: <bug-58553-4-T7vIqCm4UX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58553-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58553 Bug 58553 depends on bug 58554, which changed state. Bug 58554 Summary: [4.9 Regression] Revision 202619 causes runtime failure in CPU2006 benchmark 445.gobmk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58554 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |---
next prev parent reply other threads:[~2013-09-27 19:37 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-27 16:44 [Bug tree-optimization/58553] New: " jgreenhalgh at gcc dot gnu.org 2013-09-27 16:46 ` [Bug tree-optimization/58553] " jgreenhalgh at gcc dot gnu.org 2013-09-27 19:11 ` law at redhat dot com 2013-09-27 19:15 ` pinskia at gcc dot gnu.org 2013-09-27 19:19 ` law at redhat dot com 2013-09-27 19:33 ` law at redhat dot com 2013-09-27 19:33 ` law at redhat dot com 2013-09-27 19:37 ` law at redhat dot com [this message] 2013-09-30 7:49 ` rguenth at gcc dot gnu.org 2013-09-30 11:17 ` rguenth at gcc dot gnu.org 2013-09-30 12:43 ` rguenth at gcc dot gnu.org 2013-09-30 15:52 ` law at redhat dot com 2013-10-01 7:40 ` rguenther at suse dot de 2013-10-01 7:41 ` rguenth at gcc dot gnu.org 2013-10-01 7:59 ` rguenth at gcc dot gnu.org 2013-10-01 16:33 ` law at redhat dot com 2013-10-02 8:01 ` rguenther at suse dot de
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-58553-4-T7vIqCm4UX@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).