public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51134] [4.7 Regression] x86 memset/memcpy expansion is broken Date: Tue, 15 Nov 2011 19:57:00 -0000 [thread overview] Message-ID: <bug-51134-4-Tkla99pfAp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51134-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51134 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.7.0 Summary|[4.7 Regression] FAIL: |[4.7 Regression] x86 |gfortran.fortran-torture/ex |memset/memcpy expansion is |ecute/arrayarg.f90 |broken
next prev parent reply other threads:[~2011-11-15 19:50 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-14 23:51 [Bug target/51134] New: [4.7 Regression] FAIL: gfortran.fortran-torture/execute/arrayarg.f90 hjl.tools at gmail dot com 2011-11-15 4:15 ` [Bug target/51134] " hjl.tools at gmail dot com 2011-11-15 5:21 ` hjl.tools at gmail dot com 2011-11-15 12:40 ` hubicka at ucw dot cz 2011-11-15 14:01 ` hubicka at ucw dot cz 2011-11-15 16:44 ` hjl.tools at gmail dot com 2011-11-15 19:57 ` hjl.tools at gmail dot com [this message] 2011-11-16 5:15 ` [Bug target/51134] [4.7 Regression] x86 memset/memcpy expansion is broken hjl.tools at gmail dot com 2011-11-18 1:17 ` hubicka at gcc dot gnu.org 2011-11-18 2:23 ` hubicka at gcc dot gnu.org 2011-11-22 5:31 ` hjl.tools at gmail dot com 2011-11-22 14:19 ` michael.v.zolotukhin at gmail dot com 2011-11-22 16:43 ` hjl.tools at gmail dot com 2011-11-22 17:23 ` michael.v.zolotukhin at gmail dot com 2011-11-24 22:21 ` hjl at gcc dot gnu.org 2011-11-25 2:03 ` hjl.tools 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-51134-4-Tkla99pfAp@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).