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 tree-optimization/65506] New: FAIL: gcc.dg/pr29215.c scan-tree-dump-not gimple "memcpy" Date: Sat, 21 Mar 2015 20:43:00 -0000 [thread overview] Message-ID: <bug-65506-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65506 Bug ID: 65506 Summary: FAIL: gcc.dg/pr29215.c scan-tree-dump-not gimple "memcpy" Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org Host: hppa-unknown-linux-gnu Target: hppa-unknown-linux-gnu Build: hppa-unknown-linux-gnu Created attachment 35088 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35088&action=edit Gimple dump spawn /home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc/ /home/ dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/pr29215.c -fno-diagnostics-show-caret -fdi agnostics-color=never -O2 -fdump-tree-gimple -S -o pr29215.s PASS: gcc.dg/pr29215.c (test for excess errors) FAIL: gcc.dg/pr29215.c scan-tree-dump-not gimple "memcpy" This is revision 221548. Revision 221505 was okay.
next reply other threads:[~2015-03-21 18:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-21 20:43 danglin at gcc dot gnu.org [this message] 2015-03-23 9:55 ` [Bug tree-optimization/65506] [5 Regression] " rguenth at gcc dot gnu.org 2015-03-23 14:25 ` [Bug testsuite/65506] " jakub at gcc dot gnu.org 2015-03-23 15:32 ` rguenth at gcc dot gnu.org 2015-03-23 15:33 ` dave.anglin at bell dot net 2015-03-23 21:32 ` jakub at gcc dot gnu.org 2015-03-23 22:29 ` jakub at gcc dot gnu.org 2015-03-24 0:10 ` olegendo at gcc dot gnu.org 2015-03-25 14:07 ` alalaw01 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-65506-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).