public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45266] New: [4.6 regression] FAIL: gfortran.dg/array_memcpy_3.f90 Date: Thu, 12 Aug 2010 15:43:00 -0000 [thread overview] Message-ID: <bug-45266-682@http.gcc.gnu.org/bugzilla/> (raw) On Linux/x86-64, revision 163191 gave FAIL: gfortran.dg/array_memcpy_3.f90 -O scan-tree-dump-times original "memcpy|(ref-all.*ref-all)" 2 FAIL: gfortran.dg/array_memcpy_3.f90 -O scan-tree-dump-times original "memcpy|(ref-all.*ref-all)" 2 Revision 163187 is OK. This may be caused by revision 163189: http://gcc.gnu.org/ml/gcc-cvs/2010-08/msg00400.html Linux/ia32 doesn't have this regression. -- Summary: [4.6 regression] FAIL: gfortran.dg/array_memcpy_3.f90 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45266
next reply other threads:[~2010-08-12 15:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-12 15:43 hjl dot tools at gmail dot com [this message] 2010-08-12 15:47 ` [Bug testsuite/45266] " rguenth at gcc dot gnu dot org 2010-08-12 15:49 ` [Bug middle-end/45266] " hjl dot tools at gmail dot com 2010-08-12 15:50 ` [Bug testsuite/45266] " rguenth at gcc dot gnu dot org 2010-08-12 16:44 ` [Bug middle-end/45266] " hjl dot tools at gmail dot com 2010-08-12 18:17 ` [Bug testsuite/45266] " rguenth at gcc dot gnu dot org 2010-08-13 12:35 ` rguenth at gcc dot gnu dot org 2010-08-13 22:39 ` sje at cup dot hp dot com 2010-08-16 17:12 ` sje at cup dot hp dot com 2010-08-17 9:48 ` rguenth at gcc dot gnu dot org 2010-08-17 10:47 ` jakub at gcc dot gnu dot 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-45266-682@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).