public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23302] [4.1 Regression] extra move generated on x86
Date: Mon, 31 Oct 2005 18:15:00 -0000 [thread overview]
Message-ID: <20051031181524.12859.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23302-1008@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from hubicka at gcc dot gnu dot org 2005-10-31 18:15 -------
Actually the cited 4.0 sequence do not obey the const int x86_read_modify =
~(m_PENT | m_PPRO);
setting -march=athlon or using -Os makes the move go away. Additionally I get
following sequence out of 4.0 in SUSE distro:
movl term, %eax
movl 4012(%ebx), %ecx
movl 4028(%eax), %eax
imull %ecx, %eax
that also contains the extra memory move.
So I am going to close this as invalid.
Honza
--
hubicka at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23302
next prev parent reply other threads:[~2005-10-31 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23302-1008@http.gcc.gnu.org/bugzilla/>
2005-10-17 9:31 ` steven at gcc dot gnu dot org
2005-10-31 4:43 ` mmitchel at gcc dot gnu dot org
2005-10-31 18:15 ` hubicka at gcc dot gnu dot org [this message]
2005-08-09 22:05 [Bug rtl-optimization/23302] New: " dann at godzilla dot ics dot uci dot edu
2005-08-10 0:06 ` [Bug target/23302] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-28 16:52 ` hubicka at gcc dot gnu dot org
2005-09-28 16:52 ` hubicka at gcc dot gnu dot org
2005-09-28 17:30 ` dann at godzilla dot ics dot uci dot edu
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=20051031181524.12859.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).