public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <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: Fri, 18 Nov 2011 02:23:00 -0000 [thread overview] Message-ID: <bug-51134-4-Go7gH97OP6@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 --- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-11-18 02:18:32 UTC --- Author: hubicka Date: Fri Nov 18 02:18:28 2011 New Revision: 181466 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181466 Log: PR bootstrap/51134 * i386.c (atom_cost): Fix 32bit memset description. (expand_set_or_movmem_via_loop_with_iter): Output proper bounds check for epilogue loops. (expand_movmem_epilogue): Handle epilogues up to size 15 w/o producing byte loop. (decide_alg): sse_loop is not useable wthen SSE2 is disabled; when not optimizing always use rep movsb or lincall; do not produce word sized loops when optimizing memset for size (to avoid need for large constants). (ix86_expand_movmem): Get into sync with ix86_expand_setmem; choose unroll factors better; always do 128bit moves when producing SSE loops; do not produce loopy epilogue when size is too small. (promote_duplicated_reg_to_size): Do not look into desired alignments when doing vector expansion. (ix86_expand_setmem): Track better when promoted value is available; choose unroll factors more sanely.; output loopy epilogue only when needed. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c
next prev parent reply other threads:[~2011-11-18 2:19 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 ` [Bug target/51134] [4.7 Regression] x86 memset/memcpy expansion is broken hjl.tools at gmail dot com 2011-11-16 5:15 ` 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 [this message] 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-Go7gH97OP6@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).