public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15184] [3.3/3.4/3.5 Regression] Direct access to byte inside word not working with -march=pentiumpro
Date: Wed, 28 Apr 2004 00:33:00 -0000	[thread overview]
Message-ID: <20040427235537.719.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040427233827.15184.cesarb@nitnet.com.br>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-27 23:55 -------
Confirmed a regression from 2.95.3.  For some werid reason -march=pentium4 works.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|optimization                |target
     Ever Confirmed|                            |1
 GCC target triplet|                            |pentiumpro-*-*
           Keywords|                            |pessimizes-code
      Known to fail|                            |3.0.4 3.2.3 3.3.1 3.3.3
                   |                            |3.4.0 3.5.0
      Known to work|                            |2.95.3
   Last reconfirmed|0000-00-00 00:00:00         |2004-04-27 23:55:37
               date|                            |
            Summary|Direct access to byte inside|[3.3/3.4/3.5 Regression]
                   |word not working with -     |Direct access to byte inside
                   |march=pentiumpro            |word not working with -
                   |                            |march=pentiumpro
   Target Milestone|---                         |3.3.4


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15184


  reply	other threads:[~2004-04-27 23:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 23:52 [Bug optimization/15184] New: " cesarb at nitnet dot com dot br
2004-04-28  0:33 ` pinskia at gcc dot gnu dot org [this message]
2004-04-28  0:42 ` [Bug target/15184] [3.3/3.4/3.5 Regression] " cesarb at nitnet dot com dot br
2004-05-17 10:47 ` [Bug target/15184] [3.4/3.5 " gdr at gcc dot gnu dot org
2004-06-12 22:53 ` mmitchel at gcc dot gnu dot org
2004-06-21 21:20 ` mmitchel at gcc dot gnu dot org
2004-08-29 18:58 ` mmitchel at gcc dot gnu dot org
2004-11-01  0:46 ` [Bug target/15184] [3.4/4.0 " mmitchel at gcc dot gnu dot org
2005-02-25  2:06 ` rth at gcc dot gnu dot org
2005-05-19 17:30 ` [Bug target/15184] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-22 21:18 ` pinskia at gcc dot gnu dot org
2005-09-27 16:13 ` mmitchel 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=20040427235537.719.qmail@sources.redhat.com \
    --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).