public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/21138] wrong code in sixtrack for -fmodulo-sched
Date: Fri, 22 Apr 2005 00:26:00 -0000	[thread overview]
Message-ID: <20050422002631.8296.qmail@sourceware.org> (raw)
In-Reply-To: <20050421005103.21138.janis@gcc.gnu.org>


------- Additional Comments From janis at gcc dot gnu dot org  2005-04-22 00:26 -------
The testcase starts failing with this patch from rakdver:
  http://gcc.gnu.org/ml/gcc-cvs/2005-04/msg00301.html

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rakdver at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2005-04-22  0:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21  0:51 [Bug tree-optimization/21138] New: " janis at gcc dot gnu dot org
2005-04-21  0:51 ` [Bug tree-optimization/21138] " janis at gcc dot gnu dot org
2005-04-21  0:54 ` [Bug rtl-optimization/21138] " pinskia at gcc dot gnu dot org
2005-04-22  0:26 ` janis at gcc dot gnu dot org [this message]
2005-04-22 13:56 ` rakdver at gcc dot gnu dot org
2005-04-28  0:07 ` janis at gcc dot gnu dot org
2005-05-04 12:31 ` mustafa at il dot ibm dot com
2005-05-09 19:32 ` janis at gcc dot gnu dot org
2005-05-16 20:27 ` janis at gcc dot gnu dot org
2005-05-17 15:07 ` mustafa at il dot ibm dot com
2005-05-17 20:01 ` janis187 at us dot ibm dot com
2005-06-01  5:27 ` cvs-commit at gcc dot gnu dot org
2005-06-01 19:17 ` pinskia 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=20050422002631.8296.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).