public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27567] [4.0/4.1 Regression] __builtin_memcpy generates redundant stores/moves. Date: Wed, 14 Feb 2007 09:12:00 -0000 [thread overview] Message-ID: <20070214090510.6396.qmail@sourceware.org> (raw) In-Reply-To: <bug-27567-7667@http.gcc.gnu.org/bugzilla/> -- mmitchel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.1.2 |4.1.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27567
next prev parent reply other threads:[~2007-02-14 9:12 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-11 21:47 [Bug other/27567] New: " pluto at agmk dot net 2006-05-12 8:27 ` [Bug rtl-optimization/27567] [4.0/4.1/4.2 Regression] " rguenth at gcc dot gnu dot org 2006-06-04 19:01 ` mmitchel at gcc dot gnu dot org 2006-08-27 18:59 ` pinskia at gcc dot gnu dot org 2006-08-27 19:00 ` [Bug middle-end/27567] " pinskia at gcc dot gnu dot org 2006-08-29 14:35 ` jakub at gcc dot gnu dot org 2006-08-30 15:50 ` patchapp at dberlin dot org 2006-09-02 6:55 ` jakub at gcc dot gnu dot org 2007-02-03 17:01 ` [Bug middle-end/27567] [4.0/4.1 " gdr at gcc dot gnu dot org 2007-02-03 20:32 ` pinskia at gcc dot gnu dot org 2007-02-14 9:12 ` mmitchel at gcc dot gnu dot org [this message] 2007-02-14 22:24 ` pluto at agmk dot net 2007-02-20 10:25 ` [Bug middle-end/27567] [4.0/4.1/4.2 " pluto at agmk dot net 2007-02-20 16:42 ` [Bug middle-end/27567] [4.0/4.1 " pinskia at gcc dot gnu dot org 2007-02-25 18:28 ` pluto at agmk dot net 2007-06-26 11:46 ` jakub at gcc dot gnu dot org 2008-02-20 22:38 ` rguenth 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=20070214090510.6396.qmail@sourceware.org \ --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).