public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/38708] [4.4 Regression] Revision 137646 caused gcc.c-torture/execute/memset-[23].c fail with -mtune=pentiumpro Date: Fri, 09 Jan 2009 17:13:00 -0000 [thread overview] Message-ID: <20090109171309.29981.qmail@sourceware.org> (raw) In-Reply-To: <bug-38708-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from jakub at gcc dot gnu dot org 2009-01-09 17:13 ------- Subject: Bug 38708 Author: jakub Date: Fri Jan 9 17:12:40 2009 New Revision: 143211 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143211 Log: PR target/38686 PR target/38708 * config/i386/i386.c (override_options): Reject -mstringop-strategy=rep_8byte with -m32. (ix86_expand_movmem): For size_needed == 1 set epilogue_size_needed to 1. Do count comparison against epilogue_size_needed at compile time even when count_exp was constant forced into register. For size_needed don't jump to epilogue, instead just avoid aligning and invoke the body algorithm. If need_zero_guard, add zero guard even if count is non-zero, but smaller than size_needed + number of bytes that could be stored for alignment. (ix86_expand_setmem): For size_needed == 1 set epilogue_size_needed to 1. If need_zero_guard, add zero guard even if count is non-zero, but smaller than size_needed + number of bytes that could be stored for alignment. Compare size_needed with epilogue_size_needed instead of desired_align - align, don't adjust size_needed, pass epilogue_size_needed to the epilogue expanders. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38708
next prev parent reply other threads:[~2009-01-09 17:13 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-02 18:45 [Bug target/38708] New: [4.4 Regression] gcc.c-torture/execute/memset-3.c Fails with -march=pentium-m -O1 pinskia at gcc dot gnu dot org 2009-01-02 18:49 ` [Bug target/38708] " pinskia at gcc dot gnu dot org 2009-01-02 18:51 ` pinskia at gcc dot gnu dot org 2009-01-02 19:03 ` [Bug target/38708] [4.4 Regression] Revision 137646 caused gcc.c-torture/execute/memset-[23].c fail with -mtune=pentium-m hjl dot tools at gmail dot com 2009-01-02 22:03 ` hjl dot tools at gmail dot com 2009-01-02 22:10 ` [Bug target/38708] [4.4 Regression] Revision 137646 caused gcc.c-torture/execute/memset-[23].c fail with -mtune=pentiumpro pinskia at gcc dot gnu dot org 2009-01-03 8:47 ` jakub at gcc dot gnu dot org 2009-01-03 9:10 ` jakub at gcc dot gnu dot org 2009-01-03 10:27 ` jakub at gcc dot gnu dot org 2009-01-03 10:28 ` jakub at gcc dot gnu dot org 2009-01-03 11:40 ` jakub at gcc dot gnu dot org 2009-01-04 14:26 ` jakub at gcc dot gnu dot org 2009-01-05 11:32 ` rguenth at gcc dot gnu dot org 2009-01-05 11:44 ` rguenth at gcc dot gnu dot org 2009-01-06 11:13 ` jakub at gcc dot gnu dot org 2009-01-09 17:13 ` jakub at gcc dot gnu dot org [this message] 2009-01-09 17:14 ` 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=20090109171309.29981.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).