public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18241] [4.0 Regression] linux kernel loop gets miscompiled
Date: Sat, 18 Dec 2004 12:03:00 -0000	[thread overview]
Message-ID: <20041218120314.14358.qmail@sourceware.org> (raw)
In-Reply-To: <20041031010322.18241.ak@muc.de>


------- Additional Comments From steven at gcc dot gnu dot org  2004-12-18 12:03 -------
We have reason to believe this bug is now fixed, but it is kind of 
hard to test...  Can you please retry with CVS HEAD? 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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


  parent reply	other threads:[~2004-12-18 12:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31  1:03 [Bug tree-optimization/18241] New: " ak at muc dot de
2004-10-31  1:07 ` [Bug tree-optimization/18241] " ak at muc dot de
2004-10-31  4:41 ` [Bug tree-optimization/18241] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-01  2:26 ` giovannibajo at libero dot it
2004-11-01  2:29 ` giovannibajo at libero dot it
2004-11-01  2:34 ` pinskia at gcc dot gnu dot org
2004-11-01  2:36 ` pinskia at gcc dot gnu dot org
2004-11-01  3:07 ` ak at muc dot de
2004-11-01  3:08 ` ak at muc dot de
2004-11-16 17:54 ` pinskia at gcc dot gnu dot org
2004-11-25  0:22 ` ak at muc dot de
2004-11-27 23:07 ` pinskia at gcc dot gnu dot org
2004-11-28  0:17 ` ak at muc dot de
2004-11-28  1:05 ` ak at muc dot de
2004-11-28  1:21 ` ak at muc dot de
2004-11-28  1:28 ` pinskia at gcc dot gnu dot org
2004-11-28  1:33 ` [Bug web/18241] " ak at muc dot de
2004-11-28  9:17 ` [Bug tree-optimization/18241] " rakdver at atrey dot karlin dot mff dot cuni dot cz
2004-12-13 20:46 ` law at redhat dot com
2004-12-13 21:01 ` law at redhat dot com
2004-12-13 22:16 ` law at redhat dot com
2004-12-15 15:14 ` steven at gcc dot gnu dot org
2004-12-15 15:16 ` steven at gcc dot gnu dot org
2004-12-18 12:03 ` steven at gcc dot gnu dot org [this message]
2004-12-19 15:55 ` ak at muc dot de
2005-01-03 13:41 ` arend dot bayer at web dot de
2005-01-03 13:44 ` giovannibajo at libero dot it
2005-01-03 13:55 ` arend dot bayer at web dot de
2005-01-03 19:12 ` pinskia at gcc dot gnu dot org
2005-01-03 20:46 ` belyshev at depni dot sinp dot msu dot ru
2005-01-03 21:07 ` law at redhat dot com
2005-01-03 21:10 ` pinskia at gcc dot gnu dot org
2005-01-03 22:41 ` pinskia at gcc dot gnu dot org
2005-01-03 22:59 ` steven at gcc dot gnu dot org
2005-01-03 23:27 ` belyshev at depni dot sinp dot msu dot ru
2005-01-04  0:40 ` [Bug tree-optimization/18241] [4.0 Regression] volatile causes mis-compiling pinskia at gcc dot gnu dot org
2005-01-07 15:09 ` dnovillo at gcc dot gnu dot org
2005-01-07 18:43 ` giovannibajo at libero dot it
2005-01-08 18:47 ` dnovillo 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=20041218120314.14358.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).