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: Sun, 04 Jan 2009 14:26:00 -0000 [thread overview]
Message-ID: <20090104142628.334.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38708-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from jakub at gcc dot gnu dot org 2009-01-04 14:26 -------
The problem is that if size is smaller than epilogue_size_needed, desired_align
> align and size_needed == 1, then ix86_expand_setmem jumps around the
initialization of promoted_val (when val_exp isn't CONST_INT) and alignment,
but then uses promoted_val for rep stosb (which is thus uninitialized).
I have a fix.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2009-01-02 19:01:18 |2009-01-04 14:26:28
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38708
next prev parent reply other threads:[~2009-01-04 14:26 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 [this message]
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
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=20090104142628.334.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: link
Be 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).